Jump to: navigation, search

Difference between revisions of "Gyrex/Contributor Guide/Releng"

(Publishing Builds on download.eclipse.org)
m
Line 3: Line 3:
 
== Publishing Builds on download.eclipse.org ==
 
== Publishing Builds on download.eclipse.org ==
 
Builds get published automatically on download.eclipse.org. However, only I-Builds run automatically once per week. All other builds must be triggered '''manually'''.
 
Builds get published automatically on download.eclipse.org. However, only I-Builds run automatically once per week. All other builds must be triggered '''manually'''.
{| class="wikitable"
+
{|{{BMTableStyle}}
 
|+Build Types and Hudson job parameter
 
|+Build Types and Hudson job parameter
|-
+
|-{{BMTHStyle}}
 
|Parameter
 
|Parameter
 
|Description
 
|Description

Revision as of 15:09, 27 January 2014

Please read through the following to get a better understanding of how releases are done.

Publishing Builds on download.eclipse.org

Builds get published automatically on download.eclipse.org. However, only I-Builds run automatically once per week. All other builds must be triggered manually.

Build Types and Hudson job parameter
Parameter Description Integration Builds
BUILD_TYPE The type of a build. I
BUILD_IDENTIFIER A specific identifier to label the build or empty to generate a default one. (leave empty)
BUILD_BRANCH The branch to build from. should always be master
PUBLISH_STREAM The stream this gets published to on download.eclipse.org/gyrex/$PUBLISH_STREAM/... should be the upcoming minor release (eg. 1.3) without last version component, just major.minor