hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Lucene-hadoop Wiki] Update of "HudsonBuildServer" by NigelDaley
Date Thu, 16 Aug 2007 16:55:43 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-hadoop Wiki" for change notification.

The following page has been changed by NigelDaley:

The comment on the change is:
Added info on properly stopping nightly and patch builds

  Most tasks, such as creating a new build or modifying an existing build, are performed through
the Hudson web interface.  Once you login to Hudson, you are provided with an expanded number
of administration options.  To create a login on Hudson, see below.  The following tasks must
be performed after logging into {{{lucene.zones.apache.org}}} and switching to the {{{hudson}}}
-    1. '''Killing a nightly build:'''
+    1. '''Stopping a nightly build:'''
-       PENDING
+       When logged into Hudson, a red X button is displayed next to each running build. 
Clicking the button will end the build as far as Hudson is concerned, but the underlying processes
sometimes don't get properly terminated.  A better approach is to kill the {{{build-test.sh}}}
process (used by some builds) or, if that doesn't exist, the {{{ant}}} process:
+          1. Login to {{{lucene.zones.apache.org}}}
+          1. Switch to the {{{hudson}}} user
+          1. {{{ps -ef | grep hudson}}} to get the {{{build-test.sh}}} or {{{ant}}} process
+          1. {{{kill [-9] <build-test.sh or ant process id>}}}
+          1. {{{ps -ef | grep hudson}}} again to verify the build and test processes are
gone.  The only remaining java process should be the Tomcat process ({{{org.apache.catalina.startup.Bootstrap}}}).
+       When this process dies, Hudson will fail the build.
-    1. '''Killing a patch build:'''
+    1. '''Stopping a patch build:'''
-       PENDING
+       Follow the same advice for stopping a nightly build (above) but include these additional
steps once the running patch build is terminated:
+          1. {{{cd ~hudson/hudson/jobs/Hadoop-Patch/}}}
+          1. {{{ls -al current}}} to see which directory the {{{current}}} link is pointing
+          1. {{{rm -rf <directory that current points to> current}}} to delete both
the directory and the {{{current}}} link
+       Once the {{{current}}} link is gone, a waiting {{{processEmail.sh}}} process will
create a new {{{current}}} link and start the next patch build.
     1. '''Creating a login on Hudson:'''
        Committers can create a Hudson login for themselves by adding an entry to the Tomcat
users list located in {{{~hudson/tools/tomcat/apache-tomcat-5.5.20/conf/tomcat-users.xml}}}.
 Simply copy and edit an existing entry.  Once your entry is added, Tomcat must be restarted
(see below for instructions to perform this task).  Once Tomcat is restarted, you can then
login to the web interface.

View raw message