MoDisco/Releng/How it Works
Nightly builds job (cbi-modisco-nightly)
- Everything starts from Hudson (see the nightly Hudson Job configuration ), which runs on the Eclipse build server (build.eclipse.org).
- The build is started on a defined schedule (every 6 hours), but can also be started manually.
- Hudson first exports the contents of the MoDisco SVN  to its Workspace (
/opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/workspace). If the build was started automatically and nothing changed on the SVN since the last build, then the build job stops there.
- The Hudson job is configured to execute a shell script that:
- imports and runs the </code>/opt/public/cbi/build/org.eclipse.dash.common.releng/hudson/run.sh</code> script
- reads the next build number from
/opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/nextBuildNumber, and decrements it to find the current build number
- looks at the log
/opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/builds/$buildNumber/logto determine if the build failed or succeeded
- exits with an error code if the build failed
- touches the
/opt/public/modeling/gmt/modisco/modiscoBuildPromoteSignalNfile if the build succeeded
Integration builds job (cbi-modisco-integration)
A little different from the nightly build job (apart from the file paths):
- Configuration : 
- The build is started once a week
- Hudson first exports the contents of the Releng project  to its Workspace (
/opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-integration/workspace). If the build was started automatically and nothing changed in the Releng project since the last build, then the build job stops there. This allows the integration job to start if the map files have changed.
- touches the
/opt/public/modeling/gmt/modisco/modiscoBuildPromoteSignalIfile if the build succeeded
Once the Hudson job is finished, the build results are found in
The following entry was added to a crontab (
*/5 * * * * /opt/public/modeling/gmt/modisco/cronPromote.sh
So that the
cronPromote.sh executes every five minutes on the build server.
This script compares the date of the signal files (modiscoBuildPromoteSignalN and modiscoBuildPromoteSignalI) touched by the Hudson script at the end of each build.
with the date of a reference file touched at the end of each promote (
It then promotes the result of the build by calling ant on the promote.xml of the Releng project, passing it the promote-N.properties for a nightly build or promote-I.properties for an integration build.
The promote is not done directly from Hudson because it does not have the necessary rights.
promote-I.properties define where to get the files from, where to put the archives and update site, and whether to add to or replace the existing contents.
cronPromote.sh script logs everything it does to
/opt/public/modeling/gmt/modisco/log-cronPromote, and trims this log file regularly to keep about the last 10 days of log. It also logs the ant output in a file in
Additionally, it removes old nightly and integration builds on the download server, keeping the last 5.
On Windows, use [www.cygwin.com/ Cygwin] for ssh and scp.
Logging in to the build server:
ssh <committerid>@build.eclipse.org <type password...>
Copying a file from the build server (example):
scp <committerid>@build.eclipse.org:/opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-integration/config.xml .
Retrieving the last successful build from the build server:
scp -r <committerid>@build.eclipse.org:/opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-integration/lastSuccessful/archive/build/* .
Sending a file to the build server:
scp archive.tgz <committerid>@build.eclipse.org:
Sending a directory to the build server:
scp -r directory <committerid>@build.eclipse.org:
Hudson saves its configuration in
/opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/config.xml for the nightly job and
/opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-integration/config.xml for the integration job.
Hudson important parameters
Files to archive =
build/?20*/** : archive the results of the build
Excludes (below "Files to archive", click on Advanced) =
build/?20*/eclipse, build/?20*/eclipse/**, build/?20*/testing, build/?20*/testing/**, build/?20*/*-AllFeaturesAndPlugins-*.zip*, build/?20*/*-Master-*.zip*, build/?20*/noclean : don't archive work directories, that are leftover by Athena when the build failed.
Test report XMLs =
build/?20*/testresults/xml/*.xml : the test results, that will be displayed in Hudson
Repository URL =
http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modiscofor the nighty build, so that a nightly build starts if the MoDisco repository changed
http://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/releng/trunk/org.eclipse.gmt.modisco.relengfor the integration build, so that a build starts only if the releng project (that is, maps) changed
# configuration export PROJRELENGROOT='-projRelengRoot svn://dev.eclipse.org/svnroot/modeling/org.eclipse.gmt.modisco/releng/trunk' export PROJRELENGPATH='-projRelengPath org.eclipse.gmt.modisco.releng' promoteSignal=/opt/public/modeling/gmt/modisco/modiscoBuildPromoteSignalN # parameters #export SNAPSHOT="true" # run the build . /opt/public/cbi/build/org.eclipse.dash.common.releng/hudson/run.sh read nextBuildNumber < /opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/nextBuildNumber buildNumber=$((nextBuildNumber-1)) # Test if build succeeded. If not, then exit with error 1. # Copy the log, because the commands appear in the grepped log... tmpLog=`mktemp` || exit 1 cat /opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/builds/$buildNumber/log > $tmpLog grep "BUILD FAILED" $tmpLog && exit 1 grep "BUILD SUCCESSFUL" $tmpLog || exit 1 #triggers promoting the build by a script waiting for the modification date of this file to change touch $promoteSignal