Upgrading Jenkins - Revision history

Dirk: link to Jenkins article

2011-05-28T21:31:33Z

link to Jenkins article

Dirk: Hudson -> Jenkins

2011-03-19T13:08:38Z

Hudson -> Jenkins

Dirk: Hudson -> Jenkins; to do: replace screenshot (waiting for the next update ...)

2011-02-07T10:39:30Z

Hudson -> Jenkins; to do: replace screenshot (waiting for the next update ...)

Dirk: Upgrading Hudson moved to Upgrading Jenkins: Hudson is now Jenkins

2011-02-07T10:36:26Z

Upgrading Hudson moved to Upgrading Jenkins: Hudson is now Jenkins

Dirk: added a screenshot of an update notice

2010-09-10T09:13:43Z

added a screenshot of an update notice

Dirk: Upgrading Hudson

2010-09-10T09:10:22Z

Upgrading Hudson

New page

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 ==

# log into Hudson
# click on the '''Manage Hudson''' 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

Now, unlike on some other systems, 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)
# do a <tt>ps ax | grep java</tt> to get the pid of the currently running Hudson process
# <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
# 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.

[[Category:Internals]]

← Older revision		Revision as of 21:31, 28 May 2011
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://jenkins-ci.org/~~ Jenkins]. Here's a quick description of the procedure to update Jenkins:	+	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:

@@ Line 6: / Line 6: @@
 # log into Jenkins
 # 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:JenkinsUpdate.png]]
 # if it does, click on the "Upgrade Automatically" button
 # wait for the download to finish

@@ 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]]
 # if it does, click on the "Upgrade Automatically" button
 # 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)
-# 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)
-# 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 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.
 [[Category:Internals]]

← Older revision	Revision as of 10:36, 7 February 2011
(No difference)