Skip to main content

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.

Jump to: navigation, search

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

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'''.
 +
 +
=== Hudson: gyrex-latest ===
 +
For producing development, milestone and major or minor release builds (no service releases). <br>
 +
https://hudson.eclipse.org/gyrex/job/gyrex-latest/
 
{|{{BMTableStyle}}
 
{|{{BMTableStyle}}
|+https://hudson.eclipse.org/gyrex/job/gyrex-latest/
 
 
|-{{BMTHStyle}}
 
|-{{BMTHStyle}}
 
|Parameter
 
|Parameter
 
|Description
 
|Description
 
|Integration Builds
 
|Integration Builds
|Stable Builds
+
|Milestone Builds
 +
|Release Builds
 
|-
 
|-
 
|BUILD_TYPE
 
|BUILD_TYPE
Line 15: Line 19:
 
|I
 
|I
 
|S
 
|S
 +
|R
 
|-
 
|-
 
|BUILD_IDENTIFIER
 
|BUILD_IDENTIFIER
Line 20: Line 25:
 
|(leave empty)
 
|(leave empty)
 
|''upcoming minor'' release (eg. 1.3) '''plus''' ''suffix'' (eg. M1, M2, ... RC1, RC2...) without space (eg. 1.3M1, 2.0RC1, ...)
 
|''upcoming minor'' release (eg. 1.3) '''plus''' ''suffix'' (eg. M1, M2, ... RC1, RC2...) without space (eg. 1.3M1, 2.0RC1, ...)
 +
|''major.minor'' for minor and major releases (eg. 1.3, 2.0); note: see below for service releases
 
|-
 
|-
 
|BUILD_BRANCH
 
|BUILD_BRANCH
 
|The branch to build from.
 
|The branch to build from.
|colspan="2"|should always be '''master'''
+
|colspan="3"|should always be '''master''' (until instructed/discussed otherwise)
 
|-
 
|-
 
|PUBLISH_STREAM
 
|PUBLISH_STREAM
 
|The stream this gets published to on <code>download.eclipse.org/gyrex/$PUBLISH_STREAM/...</code>
 
|The stream this gets published to on <code>download.eclipse.org/gyrex/$PUBLISH_STREAM/...</code>
|colspan="2"|should be the ''upcoming minor'' release (eg. 1.3) without last version component, just <code>major.minor</code>
+
|colspan="3"|should be the ''upcoming minor'' release (eg. 1.3) without last version component, just <code>major.minor</code>
 +
|}
 +
 
 +
 
 +
=== Hudson: gyrex-maintenance ===
 +
For producing service releases and maintenance builds out of the maintenance branch.<br>
 +
https://hudson.eclipse.org/gyrex/job/gyrex-maintenance/
 +
{|{{BMTableStyle}}
 +
|-{{BMTHStyle}}
 +
|Parameter
 +
|Description
 +
|Integration Builds
 +
|Milestone Builds
 +
|Release Builds
 +
|-
 +
|BUILD_TYPE
 +
|The type of a build.
 +
|M
 +
|R
 +
|-
 +
|BUILD_IDENTIFIER
 +
|A specific identifier to label the build or empty to generate a default one.
 +
|(leave empty)
 +
|''major.minor.service'', i.e. exact release version of service releases (eg. 1.3.1, 2.0.1, 2.1.4)
 +
|-
 +
|BUILD_BRANCH
 +
|The branch to build from.
 +
|colspan="3"|should be the ''"current"'' maintenance branch (eg. "maintenance/1.3" for 1.3.x builds)
 +
|-
 +
|PUBLISH_STREAM
 +
|The stream this gets published to on <code>download.eclipse.org/gyrex/$PUBLISH_STREAM/...</code>
 +
|colspan="3"|should be the ''current minor'' release stream (eg. 1.3 for 1.3.x builds) without last version component, just <code>major.minor</code>
 
|}
 
|}

Revision as of 02:55, 28 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.

Hudson: gyrex-latest

For producing development, milestone and major or minor release builds (no service releases).
https://hudson.eclipse.org/gyrex/job/gyrex-latest/

Parameter Description Integration Builds Milestone Builds Release Builds
BUILD_TYPE The type of a build. I S R
BUILD_IDENTIFIER A specific identifier to label the build or empty to generate a default one. (leave empty) upcoming minor release (eg. 1.3) plus suffix (eg. M1, M2, ... RC1, RC2...) without space (eg. 1.3M1, 2.0RC1, ...) major.minor for minor and major releases (eg. 1.3, 2.0); note: see below for service releases
BUILD_BRANCH The branch to build from. should always be master (until instructed/discussed otherwise)
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


Hudson: gyrex-maintenance

For producing service releases and maintenance builds out of the maintenance branch.
https://hudson.eclipse.org/gyrex/job/gyrex-maintenance/

Parameter Description Integration Builds Milestone Builds Release Builds
BUILD_TYPE The type of a build. M R
BUILD_IDENTIFIER A specific identifier to label the build or empty to generate a default one. (leave empty) major.minor.service, i.e. exact release version of service releases (eg. 1.3.1, 2.0.1, 2.1.4)
BUILD_BRANCH The branch to build from. should be the "current" maintenance branch (eg. "maintenance/1.3" for 1.3.x builds)
PUBLISH_STREAM The stream this gets published to on download.eclipse.org/gyrex/$PUBLISH_STREAM/... should be the current minor release stream (eg. 1.3 for 1.3.x builds) without last version component, just major.minor

Back to the top