Skip to main content
Jump to: navigation, search

EMF Facet/Releng/How to Use

The EMF Facet project is built using Buckminster, with this releng project.

EMF Facet uses the same build system as MoDisco. So, for more explanation about how the build process works, see also MoDisco Releng : How it Works.

What is built?

Two features are built:

  • org.eclipse.emf.facet.all.feature

They are referenced as root dependencies in buckminster.cspec.

These features must include all other features that must be built, either directly or indirectly.

The releng project contains a Buckminster rmap, which specifies how to get the plug-ins and features that are to be built. For each plug-in or feature, the map defines its location on a version control system (CVS, SVN).

The rmap also specifies the update sites from which to retrieve the binary dependencies from the dependent projects.

Updating the rmap

The rmap reflects the dependencies on the other projects. So, it must be updated at least before each milestone, to make sure that the code that is built works with the latest versions of all the dependencies.

The easiest way to update the dependencies is to copy them from the aggregation build model, which all projects must fill in with the correct reference to their update site(s) and feature(s).

This model is in a project with the release name on the Eclipse CVS:

There is a tool that copies most of the information automatically in this plug-in:

Warning: don't forget to update the aggregation model project before copying information from it

A few dependencies are not in the aggregation build model though, so they must be updated manually:

Finding dependencies

If you don't know where a particular plug-in or feature is located, the easiest way to find it is to search the Eclipse download area using "find" on For example, to look for "" :

find /home/data/httpd/ -name 'org.eclipse.emf.compare_*'

How to start a build?


45 2-23/3 * * *

  • Nightly builds are run every 3 hours everyday, if the EMF Facet SVN changed since the last build.
  • Integration builds are started manually, usually to prepare a milestone or release



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


Successful Nightly and Integration builds are automatically published to For example, a nightly build for version 0.1.0, created on April 21 2011 at 04:13 would be published to:

These builds can then be seen and downloaded from, where additional information is available (test results, build log), or installed from the update site:

The publication is done by a script running as a cronjob under user nbros:

*/5 * * * * /opt/public/modeling/emft/facet/ runs which does the actual publication, and sends a mail to team members if the publication failed.

To re-run the publication of the last nightly build, log in to, and do:

cd /opt/public/modeling/emft/facet/
touch promoteSignalN && ./


Stable, Maintenance and Release builds are not automatically published. They should be first tested internally before publishing. For example, to publish the 0.1.0M6 milestone build:

  • First, fetch the build archive to test (from Hudson, or using wget or scp for example):

or, if https access doesn't work, a NFS access can be used (from For example:

cp /shared/jobs/emffacet-nightly/lastSuccessful/archive/ .
  • Then, test the build locally
  • Then, publish it:
ssh <commiterid>
unzip -d /home/data/httpd/

Add a new update site with the new build to the composite:

  • unzip the content (the update site zip that was in the first zip) in a new folder with the release number:
unzip -d /home/data/httpd/
  • update both the compositeContent.xml and compositeArtifacts.xml files of the update site (that are located in the parent of the folder to which you extracted the update site) to add a reference to your newly added update site
    • set the value of p2.timestamp to the result of "date +%s000"
    • increase the "size" attribute of the children element
    • add a "child" element inside the "children" element with a "location" set to the name of the folder (e.g "SR1_RC3")
  • You can enable download stats on the repository by running /opt/public/modeling/emft/facet/ on the update site
  • Check that the new build appears on
  • Builds can be hidden from this page before a release by modifying downloads-scripts.php in www/modeling/emft/facet/downloads/ on
  • Update the archive site with the new build:
    • unzip -d /home/data/httpd/
    • update /home/data/httpd/ with a link to the newly added update zip
  • Tag the build

Simultaneous Release

If the build must be part of the simultaneous release, you must also:


There are no "release builds". The release is a release candidate that is promoted to an actual release by following these steps:

  • copy the last release candidate's update site (e.g downloads/facet/updates/milestones/0.1/SR2_RC4) to a release update site (e.g downloads/facet/updates/release/0.1.2/)
  • fix the "p2.mirrorsURL" in the release update site's artifacts.jar, so that it matches the update site's location. For example:
<property name="p2.mirrorsURL" value=";format=xml&amp;protocol=http"/>
  • copy the last release candidate drop (e.g downloads/facet/downloads/drops/0.1.2/S201202140309) to a release drop (e.g downloads/facet/downloads/drops/0.1.2/R201202140309).
  • rename the update site in the drop so that it doesn't have a RCx suffix. E.g: R201202140309/

The release process for the simultaneous release is a bit more involved. The process is usually documented in a document on the wiki named "<release> final daze". E.g It consists of:

  • when creating the release update site, do not add the release update site to its parent composite yet: this must be done on the release day (when announced on the cross-project-issues-dev mailing list), in order to let mirroring complete before users try to download the bits
  • hide the drops from the download page, by modifying the PHP script for the download page:
    • uncomment the line that contains the comment "XXX hide release until release day", and set the release folder to hide

Then during the "quiet week"

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.); leave it blank for nightly and integration builds
  • SIGN_UPDATE_SITE : whether to sign the update site (can take up to an hour on the Eclipse build server); mandatory for all builds except nightlies
  • VERSION : the version being built. Dictates in which folder the build will be placed under the download "drops" folder.


Releases should have a tag like R0_1_0, and milestones should have a tag like S0_1_0M7.

Tag names
Since the tag name is used as a bundle qualifier by PDE Build, it should not contain periods. For example, use R0_1_0 instead of v0.1.0


Check 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

or for plug-ins in your workspace:

find $workspaceRoot -name '' | while read i; do grep -q about.html "$i" || echo "$i"; done

Check licenses

find $workspaceRoot -type f -name 'license.html' | while read i; do md5 $i; done

Check Manifest.MF

find $workspaceRoot -name 'MANIFEST.MF' | while read i; do grep -q Bundle-Vendor "$i" || echo "$i"; done
find $workspaceRoot -name 'feature.xml' | while read i; do grep -q provider-name "$i" || echo "$i"; done

Check p2.mirrorsURL

find . -type f -name 'artifacts.jar' -or -name 'artifacts.xml' | while read i; do 
  echo "$i"
  if  "$i" =~ .*/artifacts.jar ; then echo "  "$(unzip -p "$i"|grep "p2.mirrorsURL")
  else echo "  "$(cat "$i"|grep "p2.mirrorsURL"); fi

Check simrel reports

for url in \
   "" \
   "" \
   "" \
   "" \
   "" \
  echo "checking $url"
  curl -s -S "$url" | egrep 'modisco|facet'
echo "checking $url"
curl -s -S $url > licenseConsistency
n=$(cat licenseConsistency | grep -n "Features with matching" | sed 's/:.*//')
cat licenseConsistency | head -n $n | egrep 'modisco|facet'
echo "checking $url"
curl -s -S $url > featureNames
n=$(cat featureNames | grep -n "Probably correct names" | sed 's/:.*//')
cat featureNames | head -n $n | egrep 'modisco|facet'
echo "checking $url"
curl -s -S $url > bundleNames
n=$(cat bundleNames | grep -n "Probably correct bundle name" | sed 's/:.*//')
cat bundleNames | head -n $n | egrep 'modisco|facet'
echo "checking $url"
curl -s -S $url > providerNames
n=$(cat providerNames | grep -n "Probably using correct provider name" | sed 's/:.*//')
cat providerNames | head -n $n | egrep 'modisco|facet'
echo "checking $url"
curl -s -S $url > copyrights
n=$(cat copyrights | grep -n "Features with copyrights that are probably ok" | sed 's/:.*//')
cat copyrights | head -n $n | egrep 'modisco|facet'
echo "checking $url"
curl -s -S $url > esdata
n=$(cat esdata | grep -n "Bundles without an Eclipse-SourceReference" | sed 's/:.*//')
cat esdata | tail -n +$n | egrep 'modisco|facet'

Back to the top