Difference between revisions of "Upgrading Jenkins"

From GeeklogWiki
Jump to: navigation, search
m (Upgrading Hudson moved to Upgrading Jenkins: Hudson is now Jenkins)
(Hudson -> Jenkins; to do: replace screenshot (waiting for the next update ...))
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://jenkins-ci.org/ Jenkins]. Here's a quick description of the procedure to update Jenkins:
  
  
== Upgrading Hudson ==
+
== Upgrading Jenkins ==
  
# log into Hudson
+
# log into Jenkins
# click on the '''Manage Hudson''' link (proper permissions required)
+
# click on the '''Manage Jenkins''' link (proper permissions required)
 
# see if it offers any updates [[image:HudsonUpdate.png]]
 
# 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
  
Next, Hudson has to be restarted ''manually'' to actually use the upgrade you just downloaded:
+
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 Hudson process
+
# 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>./hudson.start</tt> to re-start Hudson
+
# 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 Hudson to come back up
+
# don't panic, as it takes a few seconds for Jenkins to come back up
  
  
 
== Upgrading Plugins ==
 
== Upgrading Plugins ==
  
Upgrading Hudson plugin works pretty much the same way. The only difference is that you go to
+
Upgrading Jenkins plugin works pretty much the same way. The only difference is that you go to
:Manage Hudson > Manage Plugins
+
:Manage Jenkins > Manage Plugins
 
to check for available updates.
 
to check for available updates.
  
  
 
[[Category:Internals]]
 
[[Category:Internals]]

Revision as of 10:39, 7 February 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

  1. log into Jenkins
  2. click on the Manage Jenkins 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, Jenkins 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 Jenkins process
  3. kill it (may take a few seconds to shut down)
  4. go to the home directory and call up ./jenkins.start to re-start Jenkins
  5. 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.