Difference between revisions of "Gemini/Blueprint/Releasing"
Olaf.x100.de (Talk | contribs) (Updated with regard to the changed release process) |
Olaf.x100.de (Talk | contribs) |
||
Line 1: | Line 1: | ||
== Releasing Gemini Blueprint 2.x == | == Releasing Gemini Blueprint 2.x == | ||
− | Pre- | + | Pre-requisites: JDK 1.8. Maven 3.3.x. |
=== Step 1 - execute staging release === | === Step 1 - execute staging release === | ||
Line 15: | Line 15: | ||
=== Step 2 - publish the release (or drop it) === | === 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 | + | 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 Discard Release Job (https://hudson.eclipse.org/gemini/job/gemini-blueprint-discard-release/) with the same repository ID and the staged release version. |
[[Category:Gemini Blueprint|Blueprint]] | [[Category:Gemini Blueprint|Blueprint]] |
Revision as of 08:30, 16 March 2017
Releasing Gemini Blueprint 2.x
Pre-requisites: 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:
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 Discard Release Job (https://hudson.eclipse.org/gemini/job/gemini-blueprint-discard-release/) with the same repository ID and the staged release version.