Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: for the plan.

Jump to: navigation, search

MoDisco/Releng/How it Works

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

(for old Athena build, see this page)

Build jobs

  • 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) for the nightly build, or once a week for the integration build, but can also be started manually.
  • For the nightly build, Hudson first exports the contents of the MoDisco SVN [2] to its Workspace (/opt/users/hudsonbuild/.hudson/jobs/modisco-nightly/workspace on build1). 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:
    • Check out the releng project from $PROJRELENGROOT/org.eclipse.gmt.modisco.releng.buckminster (PROJRELENGROOT is a build parameter).
    • Remove the previous build results and work area
    • Create a by concatenating the from the releng project with properties set or found in the Hudson job.
    • Call Buckminster:
      • materializes the target platform and workspace using modisco.mspec from the releng project
      • builds the workspace (using Eclipse builders)
      • runs JUnit tests by using the org.eclipse.gmt.modisco.tests/AllTests.launch Eclipse launcher
      • builds the packed (with pack200) and optionally signed update site
    • Call ant on other.ant in the releng project, to create a JUnit report as HTML pages
    • zip the update site, and put that in another zip with the build log and test results
    • touch a file on the build server to trigger a promote script which is waiting for this file to change ( in /opt/public/modeling/mdt/modisco)


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

*/5 * * * *  /opt/public/modeling/mdt/modisco/

So that the 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 (/opt/public/modeling/gmt/modisco/lastPromoteRefN and lastPromoteRefI).

If a new build is detected this way, the script then promotes the result of this 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/mdt/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/mdt/modisco/promo_logs.

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

Hudson configuration

Hudson saves its configuration in /opt/users/hudsonbuild/.hudson/jobs/modisco-nightly/config.xml for the nightly job and /opt/users/hudsonbuild/.hudson/jobs/modisco-integration/config.xml for the integration job.

Some help with ssh and scp

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>

Back to the top