Difference between revisions of "Upgrading Jenkins"
From GeeklogWiki
(Hudson -> Jenkins; to do: replace screenshot (waiting for the next update ...)) |
(Hudson -> Jenkins) |
||
| Line 6: | Line 6: | ||
# log into Jenkins | # log into Jenkins | ||
# click on the '''Manage Jenkins''' link (proper permissions required) | # click on the '''Manage Jenkins''' link (proper permissions required) | ||
| − | # see if it offers any updates [[image: | + | # see if it offers any updates [[image:JenkinsUpdate.png]] |
# if it does, click on the "Upgrade Automatically" button | # if it does, click on the "Upgrade Automatically" button | ||
# wait for the download to finish | # wait for the download to finish | ||
Revision as of 13:08, 19 March 2011
Geeklog's unit test suite is run automatically after commits to the main Geeklog repository. This functionality is powered by Jenkins. Here's a quick description of the procedure to update Jenkins:
Upgrading Jenkins
- log into Jenkins
- click on the Manage Jenkins link (proper permissions required)
- see if it offers any updates
- if it does, click on the "Upgrade Automatically" button
- wait for the download to finish
Next, Jenkins has to be restarted manually to actually use the upgrade you just downloaded:
- log into the server, using the project management account (not your user account)
- do a ps ax | grep java to get the pid of the currently running Jenkins process
- kill it (may take a few seconds to shut down)
- go to the home directory and call up ./jenkins.start to re-start Jenkins
- don't panic, as it takes a few seconds for Jenkins to come back up
Upgrading Plugins
Upgrading Jenkins plugin works pretty much the same way. The only difference is that you go to
- Manage Jenkins > Manage Plugins
to check for available updates.
