* Nightly builds are run every 6 hours everyday, at 02:10, 08:10, 14:10 and 20:10 [http://en.wikipedia.org/wiki/Eastern_Time_Zone EST], if the [http://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.modisco MoDisco SVN] changed since the last build.

* Nightly builds are run every 6 hours everyday, at 02:10, 08:10, 14:10 and 20:10 [http://en.wikipedia.org/wiki/Eastern_Time_Zone EST], if the [http://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.modisco MoDisco SVN] changed since the last build.

−

* Integration builds are started every Friday at 14:30 EST.

+

* Integration builds are started manually.

=== Manually ===

=== Manually ===

* Only committers in the MoDisco project, and members of the Callisto-dev group can launch MoDisco build jobs from Hudson.

* Only committers in the MoDisco project, and members of the Callisto-dev group can launch MoDisco build jobs from Hudson.

These builds can then be seen and downloaded from [http://www.eclipse.org/MoDisco/downloads/ http://www.eclipse.org/MoDisco/downloads/], where additional information is available (test results, build log).

These builds can then be seen and downloaded from [http://www.eclipse.org/MoDisco/downloads/ http://www.eclipse.org/MoDisco/downloads/], where additional information is available (test results, build log).

+

+

=== With a script ===

+

Run <code>/opt/public/modeling/mdt/modisco/manualPromote.sh</code> and fill in the parameters.

* You can enable download stats on the repository by running [http://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.modisco/releng/trunk/org.eclipse.gmt.modisco.releng.buckminster/serverConfiguration/addDownloadStats.sh addDownloadStats.sh] on the update site

−

* You can enable download stats on the repository by running [http://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.modisco/releng/trunk/org.eclipse.gmt.modisco.releng.buckminster/serverConfiguration/addDownloadStats.sh addDownloadStats.sh]on the update site

+

* Check that the new build appears on [http://www.eclipse.org/MoDisco/downloads/ http://www.eclipse.org/MoDisco/downloads/].

* Check that the new build appears on [http://www.eclipse.org/MoDisco/downloads/ http://www.eclipse.org/MoDisco/downloads/].

* Builds can be hidden from this page before a release by modifying <code>downloads-scripts.php</code> in <code>www/MoDisco</code> on <code>:pserver:anonymous@dev.eclipse.org:/cvsroot/org.eclipse</code>

* Builds can be hidden from this page before a release by modifying <code>downloads-scripts.php</code> in <code>www/MoDisco</code> on <code>:pserver:anonymous@dev.eclipse.org:/cvsroot/org.eclipse</code>

** update <code>/home/data/httpd/archive.eclipse.org/modeling/mdt/modisco/downloads/index.html</code> with a link to the newly added update zip

** update <code>/home/data/httpd/archive.eclipse.org/modeling/mdt/modisco/downloads/index.html</code> with a link to the newly added update zip

+

* [[#Tagging|Tag the build]]

+

* [https://hudson.eclipse.org/hudson/job/modisco-integration/wipeOutWorkspace Wipe out the Hudson workspace] to free up room on the server.

=== Simultaneous Release ===

=== Simultaneous Release ===

−

If the build must be part of the simultaneous release, there are a few more steps to follow:

+

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

−

* Publish the update site to <code>/home/data/httpd/download.eclipse.org/modeling/mdt/modisco/updates/staging</code>

+

* Use the [[Eclipse_b3/aggregator/manual|B3 Aggregator]] (or a text editor if the modification is trivial) to [[Indigo/Contributing_to_Indigo_Build|update the build model for the aggregator]] ([http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.indigo.build/?root=Callisto after checking it out from CVS]).

−

* Use the [http://www.eclipse.org/modeling/amalgam/downloads/?project= DSL Toolkit] to [[Helios/Contributing_to_Helios_Build|update the build model for the aggregator]] ([http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.helios.build/?root=Callisto after checking it out from CVS]).

+

* Open juno.b3aggr in the B3 Aggregator editor, right-click on the first root node and select '''Validate Aggregation'''. Check in the error log that there are no errors.

== Build parameters ==

== Build parameters ==

Line 78:

Line 82:

== Tagging ==

== Tagging ==

To tag a release, use this script: [https://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.modisco/releng/trunk/org.eclipse.gmt.modisco.releng.buckminster/utils/tag.sh tag.sh].<br>

To tag a release, use this script: [https://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.modisco/releng/trunk/org.eclipse.gmt.modisco.releng.buckminster/utils/tag.sh tag.sh].<br>

−

Releases should have a tag like '''R0_7_1''', and milestones should have a tag like '''S0_8_M5'''.

+

Releases should have a tag like '''R0_7_1''', and milestones should have a tag like '''S0_9_0_M2'''.

{{warning|Tag names|Since the tag name is used as a bundle qualifier by PDE Build, it should not contain periods. For example, use '''R0_7_1''' instead of <s>v0.7.1</s>}}

{{warning|Tag names|Since the tag name is used as a bundle qualifier by PDE Build, it should not contain periods. For example, use '''R0_7_1''' instead of <s>v0.7.1</s>}}

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

Manually

Only committers in the MoDisco project, and members of the Callisto-dev group can launch MoDisco build jobs from Hudson.

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: