MoDisco/Releng/How it Works

From Eclipsepedia

Jump to: navigation, search

This page describes the build process of the MoDisco component, from a build engineering standpoint. For help on merely using the build, see How to Use?.



Nightly builds

  • Everything starts from Hudson (see the nightly Hudson Job configuration [1]), which runs on the Eclipse build server (
  • 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 [2] 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/</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/log to determine if the build failed or succeeded
    • exits with an error code if the build failed
    • touches the /opt/public/modeling/gmt/modisco/modiscoBuildPromoteSignalN file if the build succeeded


Once the Hudson job is finished, the build results are found in /opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/lastSuccessful/.

The following entry was added to a crontab (crontab -e):

*/5 * * * *  /opt/public/modeling/gmt/modisco/

So that the executes every five minutes on the build server.

This script compares the date of the signal file (modiscoBuildPromoteSignalN) 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 (/opt/public/modeling/gmt/modisco/lastPromoteRefN).

It then promotes the result of the build by calling ant on the promote.xml of the Releng project, passing it the for a nightly build or for an integration build.

The promote is not done directly from Hudson because it does not have the necessary rights.

The 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 /opt/public/modeling/gmt/modisco/promo_logs.

Additionally, it removes old nightly and integration builds on the download server, keeping the last 5.

Additional information

On Windows, use [ Cygwin] for ssh and scp.

Logging in to the build server:

ssh <committerid>
<type password...>

Copying a file from the build server (example):

scp <committerid> .

Retrieving the last successful build from the build server:

scp -r <committerid>* .

Sending a file to the build server:

scp archive.tgz <committerid>

Sending a directory to the build server:

scp -r directory <committerid>

Hudson configuration

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 =

Hudson script

# configuration
export PROJRELENGROOT='-projRelengRoot svn://'
export PROJRELENGPATH='-projRelengPath org.eclipse.gmt.modisco.releng'

# parameters
#export SNAPSHOT="true"

# run the build
. /opt/public/cbi/build/org.eclipse.dash.common.releng/hudson/

read nextBuildNumber < /opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/nextBuildNumber

# 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