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.
Difference between revisions of "Gyrex/Contributor Guide/Releng"
< Gyrex | Contributor Guide
m (→Publishing Builds on download.eclipse.org) |
|||
Line 65: | Line 65: | ||
|colspan="2"|should be the ''current minor'' release stream (eg. 1.3 for 1.3.x builds) without last version component, just <code>major.minor</code> | |colspan="2"|should be the ''current minor'' release stream (eg. 1.3 for 1.3.x builds) without last version component, just <code>major.minor</code> | ||
|} | |} | ||
+ | |||
+ | |||
+ | == Performing a Release == | ||
+ | The following outlines the steps necessary for producing a release. | ||
+ | |||
+ | === Pre-Release Steps === | ||
+ | # Publish a few milestone builds as release candidates (RC1, RC2, RC3 ...) | ||
+ | |||
+ | === Release Maven Parent and Target Platform === | ||
+ | # Update Maven <code>pom.xml</code> and remove <code>-SNAPSHOT</code> version suffix from: | ||
+ | #* <code>gyrex-releng/mavenparent/pom.xml:</code> | ||
+ | #** ''project -> version'' | ||
+ | #** ''project- > properties -> gyrex-target-platform.version'' | ||
+ | #** ''Important'': if you find any other *.version property in project- > properties containing a -SNAPSHOT suffix you '''MUST''' abort here! Revert any changes, then update those versions to the release versions and start again with publishing and testing at least one additional RC (release candidate) build! | ||
+ | #* <code>gyrex-releng/targetplatform/pom.xml:</code> | ||
+ | #** ''project -> parent -> version'' | ||
+ | # Trigger build of the following Hudson jobs: | ||
+ | ## [https://hudson.eclipse.org/gyrex/job/gyrex-maven-parent%20-%20build%20and%20deploy/ gyrex-maven-parent - build and deploy] | ||
+ | ## [https://hudson.eclipse.org/gyrex/job/gyrex-target-platform%20-%20build%20and%20deploy/ gyrex-target-platform - build and deploy] |
Revision as of 03:16, 28 January 2014
Please read through the following to get a better understanding of how releases are done.
Contents
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 |
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
|
Performing a Release
The following outlines the steps necessary for producing a release.
Pre-Release Steps
- Publish a few milestone builds as release candidates (RC1, RC2, RC3 ...)
Release Maven Parent and Target Platform
- Update Maven
pom.xml
and remove-SNAPSHOT
version suffix from:-
gyrex-releng/mavenparent/pom.xml:
- project -> version
- project- > properties -> gyrex-target-platform.version
- Important: if you find any other *.version property in project- > properties containing a -SNAPSHOT suffix you MUST abort here! Revert any changes, then update those versions to the release versions and start again with publishing and testing at least one additional RC (release candidate) build!
-
gyrex-releng/targetplatform/pom.xml:
- project -> parent -> version
-
- Trigger build of the following Hudson jobs: