Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
MoDisco/Releng/How to Use
The MoDisco project is built using Buckminster, with this releng project. (for old Athena build, see this page)
For more explanation about how the build process works, see also How it Works?.
Contents
What is built?
org.eclipse.gmt.modisco.all
is the feature that is built (defined in buckminster.cspec).
This feature must include all other features that must be built.
The releng project contains a Buckminster rmap, which specifies how to get the plugins and features that are to be built. For each plugin or feature, the map defines its location on a version control system (CVS, SVN), and the version that must be used.
How to start a build?
Automatically
- Nightly builds are run every 6 hours everyday, at 02:10, 08:10, 14:10 and 20:10 EST, if the MoDisco SVN changed since the last build.
- Integration builds are started every Friday at 14:30 EST.
Manually
- Only committers in the MoDisco project, and members of the Callisto-dev group can launch MoDisco build jobs from Hudson.
- Nightly build : go to https://build.eclipse.org/hudson/job/modisco-nightly/
- Integration build : go to https://build.eclipse.org/hudson/job/modisco-integration/
Then:
- In Hudson, click on Build Now, change the build parameters as needed (see #Build parameters), and click on Build.
- You can then click on the job name in the Build History section in the left column, and then on Console Output, to follow build progress in real time.
How to publish a build?
Automatically
Successful Nightly and Integration builds are automatically published to download.eclipse.org. For example, a nightly build for version 0.8.0, created on October 6 2009 at 11:54 EST would be published to:
http://download.eclipse.org/modeling/mdt/modisco/downloads/drops/0.8.0/N200910061154
These builds can then be seen and downloaded from http://www.eclipse.org/MoDisco/downloads/, where additional information is available (test results, build log).
Manually
Stable, Maintenance and Release builds are not automatically published. They should be first tested internally before publishing. For example, to publish the 0.8.0M2 milestone build:
- First, fetch the build archive to test (from Hudson, or using
wget
orscp
for example). - Then, test the build locally
- Then, publish it:
ssh <commiterid>@build.eclipse.org cd /opt/users/hudsonbuild/.hudson/jobs/modisco-integration/builds/2010-07-20_03-56-21/archive unzip S201007200356.zip -d /home/data/httpd/download.eclipse.org/modeling/mdt/modisco/downloads/drops/0.8.0/
- Finally, for a milestone, update the update site with the new build:
rm -rf /home/data/httpd/download.eclipse.org/modeling/mdt/modisco/updates/milestones/* unzip MODISCO-Update-0.8.0M2.zip -d /home/data/httpd/download.eclipse.org/modeling/mdt/modisco/updates/milestones/
- For a release:
- Create a new folder with the release number under /home/data/httpd/download.eclipse.org/modeling/mdt/modisco/updates/release
- update
compositeContent.xml
andcompositeArtifacts.xml
to add a reference to your newly added release
- You can enable download stats on the repository by running addDownloadStats.shon the update site
- Check that the new build appears on http://www.eclipse.org/MoDisco/downloads/.
- Builds can be hidden from this page before a release by modifying
downloads-scripts.php
inwww/MoDisco
on:pserver:anonymous@dev.eclipse.org:/cvsroot/org.eclipse
- Update the archive site with the new build:
- copy the drop folder (eg. "S200910061155") into
/home/data/httpd/archive.eclipse.org/modeling/mdt/modisco/downloads/drops/x.y.z
- update
/home/data/httpd/archive.eclipse.org/modeling/mdt/modisco/downloads/index.html
with a link to the newly added update zip
- copy the drop folder (eg. "S200910061155") into
Simultaneous Release
If the build must be part of the simultaneous release, there are a few more steps to follow:
- Publish the update site to
/home/data/httpd/download.eclipse.org/modeling/mdt/modisco/updates/staging
- Use the DSL Toolkit to update the build model for the aggregator (after checking it out from CVS).
Build parameters
Hudson builds expect these parameters:
- BUILDTYPE : the kind of build, represented by a code letter (see this page):
- N: Nightly
- I: Integration
- M: Maintenance (NOT milestone)
- S: Stable (for Milestones and Release Candidate builds)
- R: Release
- BUILD_ALIAS : the name of the release (0.8.0, 0.9.0M1, etc.); blank for nightly and integration builds
- SIGN_UPDATE_SITE : whether to sign the update site (takes about an hour on the Eclipse build server); mandatory for releases
- VERSION : the version being built. Dictates in which folder the build will be placed under the download "drops" folder.
- PROJRELENGROOT : The path on the SVN (trunk, branch or tag) from which to take the version of the releng project that must be used for this build.
Building locally
TODO
Tagging
To tag a release, use this script: tag.sh.
Releases should have a tag like R0_7_1, and milestones should have a tag like S0_8_M5.
Checking bundles
Check that each bundle contains an about.html file:
for f in $( ls *.jar ); do unzip -t $f | grep -q about.html || echo $f; done