Difference between revisions of "Upgrading Jenkins"

From GeeklogWiki
Jump to: navigation, search
(Upgrading Hudson)
 
(added a screenshot of an update notice)
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 [http://hudson-ci.org/ Hudson]. Here's a quick description of the procedure to update Hudson:
 
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 [http://hudson-ci.org/ Hudson]. Here's a quick description of the procedure to update Hudson:
 +
  
 
== Upgrading Hudson ==
 
== Upgrading Hudson ==
Line 5: Line 6:
 
# log into Hudson
 
# log into Hudson
 
# click on the '''Manage Hudson''' link (proper permissions required)
 
# click on the '''Manage Hudson''' link (proper permissions required)
# see if it offers any updates
+
# see if it offers any updates [[image:HudsonUpdate.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
  
Now, unlike on some other systems, Hudson has to be restarted ''manually'' to actually use the upgrade you just downloaded:
+
Next, Hudson 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)
Line 16: Line 17:
 
# go to the home directory and call up <tt>./hudson.start</tt> to re-start Hudson
 
# go to the home directory and call up <tt>./hudson.start</tt> to re-start Hudson
 
# don't panic, as it takes a few seconds for Hudson to come back up
 
# don't panic, as it takes a few seconds for Hudson to come back up
 +
  
 
== Upgrading Plugins ==
 
== Upgrading Plugins ==

Revision as of 09:13, 10 September 2010

Geeklog's unit test suite is run automatically after commits to the main Geeklog repository. This functionality is powered by Hudson. Here's a quick description of the procedure to update Hudson:


Upgrading Hudson

  1. log into Hudson
  2. click on the Manage Hudson link (proper permissions required)
  3. see if it offers any updates HudsonUpdate.png
  4. if it does, click on the "Upgrade Automatically" button
  5. wait for the download to finish

Next, Hudson has to be restarted manually to actually use the upgrade you just downloaded:

  1. log into the server, using the project management account (not your user account)
  2. do a ps ax | grep java to get the pid of the currently running Hudson process
  3. kill it (may take a few seconds to shut down)
  4. go to the home directory and call up ./hudson.start to re-start Hudson
  5. don't panic, as it takes a few seconds for Hudson to come back up


Upgrading Plugins

Upgrading Hudson plugin works pretty much the same way. The only difference is that you go to

Manage Hudson > Manage Plugins

to check for available updates.