f06a05d99dacaf5674347474dfb0de423a81c52e
wiki/building-and-deploying.md
| ... | ... | @@ -41,6 +41,14 @@ $ git push -f origin release:release |
| 41 | 41 | </pre> |
| 42 | 42 | |
| 43 | 43 | Give the build server some time (20-30 Minutes) until it will have the release ready. |
| 44 | + |
|
| 45 | +### Example with Hudson |
|
| 46 | +Deploying jobs from hudson to `releases.sapsailing.com` is quite simple. |
|
| 47 | + |
|
| 48 | +- login as `hudson@<build server>` |
|
| 49 | +- go to `/home/hudson/repo/jobs/{jobname}/workspace` |
|
| 50 | +- execute `./configuration/buildAndUpdateProduct.sh -n build -w trac@sapsailing.com release` for triggering the upload |
|
| 51 | + |
|
| 44 | 52 | ## Working with Environments |
| 45 | 53 | |
| 46 | 54 | There exist a number of preconfigured environment configurations at [releases.sapsailing.com/environments](http://releases.sapsailing.com/environments). Such an environment can be automagically applied to your instance by changing to the servers directory and then executing the `refreshInstance.sh` script with the parameter `install-env <environment-name>`. This will update your env.sh. Make sure to afterwards restart your server. |