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

Gemini/Blueprint/Releasing

< Gemini‎ | Blueprint
Revision as of 08:06, 16 March 2017 by Olaf.x100.de (Talk | contribs) (Updated with regard to the changed release process)

Releasing Gemini Blueprint 2.x

Pre-req's: JDK 1.8. Maven 3.3.x.

Step 1 - execute staging release

Execute the Hudson release staging build (https://hudson.eclipse.org/gemini/view/blueprint/job/gemini-blueprint-stage-release/). After execution, test the staged artifacts. Go to https://oss.sonatype.org/ and switch to the nexus managed repositories:

Gemini-blueprint-releasing-nexus-managed-repos.png

There, select the orgeclipsegemini-[NNN] repository created by the build. Download and test the artifacts contained therein: - Are all expected release artifacts contained? - Are the artifacts versioned as expected?

Step 2 - publish the release (or drop it)

If you are satisfied with the staged artifacts, copy the staging repo id (e.g., "orgeclipsegemini-1001" in /service/local/repositories/orgeclipsegemini-1001/content/). Provide this as a parameter to the Gemini Blueprint Release job (https://hudson.eclipse.org/gemini/view/blueprint/job/gemini-blueprint-release/). This will irrevocably release the artifacts to maven central. In case you want to discard the staged artifacts execute the Gemini Blueprint Drop Staged Release Job (https://hudson.eclipse.org/gemini/view/blueprint/job/gemini-blueprint-drop-staging-repository/) with the same repository ID.

Copyright © Eclipse Foundation, Inc. All Rights Reserved.