Jump to: navigation, search

MoDisco/Releng/How it Works

< MoDisco‎ | Releng
Revision as of 06:58, 9 October 2009 by Nbros.mia-software.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

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]).
  • 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/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/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/cronPromote.sh

So that the cronPromote.sh 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 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.

The 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.

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