Difference between revisions of "Upgrading Jenkins"
From GeeklogWiki
m (Upgrading Hudson moved to Upgrading Jenkins: Hudson is now Jenkins) |
m (link to Jenkins article) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | Geeklog's [[Test Suite|unit test suite]] is [http://project.geeklog.net:8080/ run automatically] after commits to [http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/ the main Geeklog repository]. This functionality is powered by [ | + | Geeklog's [[Test Suite|unit test suite]] is [http://project.geeklog.net:8080/ run automatically] after commits to [http://project.geeklog.net/cgi-bin/hgwebdir.cgi/geeklog/ the main Geeklog repository]. This functionality is powered by [[Jenkins]]. Here's a quick description of the procedure to update Jenkins: |
| − | == Upgrading | + | == Upgrading Jenkins == |
| − | # log into | + | # log into Jenkins |
| − | # click on the '''Manage | + | # 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 | ||
| − | Next, | + | 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) | # log into the server, using the project management account (not your user account) | ||
| − | # do a <tt>ps ax | grep java</tt> to get the pid of the currently running | + | # do a <tt>ps ax | grep java</tt> to get the pid of the currently running Jenkins process |
# <tt>kill</tt> it (may take a few seconds to shut down) | # <tt>kill</tt> it (may take a few seconds to shut down) | ||
| − | # go to the home directory and call up <tt>./ | + | # go to the home directory and call up <tt>./jenkins.start</tt> to re-start Jenkins |
| − | # don't panic, as it takes a few seconds for | + | # don't panic, as it takes a few seconds for Jenkins to come back up |
== Upgrading Plugins == | == Upgrading Plugins == | ||
| − | Upgrading | + | Upgrading Jenkins plugin works pretty much the same way. The only difference is that you go to |
| − | :Manage | + | :Manage Jenkins > Manage Plugins |
to check for available updates. | to check for available updates. | ||
[[Category:Internals]] | [[Category:Internals]] | ||
Latest revision as of 21:31, 28 May 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.
