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 "Papyrus/Papyrus Developer Guide/Release Standard Operating Procedure: Doc"
(→Release Plan Action) |
(→Release Plan Action) |
||
Line 67: | Line 67: | ||
# Keep the hudson job for MASTER and MASTER-EXTRA, the one that have been tagged and sign | # Keep the hudson job for MASTER and MASTER-EXTRA, the one that have been tagged and sign | ||
# Execute the publication | # Execute the publication | ||
+ | === With the script === | ||
+ | |||
+ | To publish a milestone or release from a build, you can use the manualPromote.sh for Luna, and manualPromote-mars.sh for Mars, script on: '''/opt/public/modeling/mdt/papyrus/manualPromote.sh''' | ||
+ | Start this script, and fill in the parameters in the interactive script. | ||
+ | |||
+ | For example: | ||
+ | |||
+ | $ cd /opt/public/modeling/mdt/papyrus/ | ||
+ | $ ./manualPromote.sh | ||
+ | -------------------- user parameters -------------------- | ||
+ | mainBuildNumber (the number of the "papyrus-trunk-nightly" Hudson build from which to publish the main Papyrus plug-ins): | ||
+ | ? 519 | ||
+ | extrasBuildNumber (the number of the "papyrus-trunk-extra-nightly" Hudson build from which to publish the extra Papyrus plug-ins, or 0 to not publish): | ||
+ | ? 43 | ||
+ | testsBuildNumber (the number of the "papyrus-trunk-nightly-tests" Hudson build from which to publish the test results, or 0 to not publish): | ||
+ | ? 93 | ||
+ | version (e.g. "0.9.0"): | ||
+ | ? 0.9.0 | ||
+ | updateSite (e.g. "nightly/juno", "milestones/0.9/M5", "releases/indigo/0.8.1") : | ||
+ | ? milestones/0.9/M5 | ||
+ | Are you sure you want to publish with these parameters (yes|no)? | ||
+ | ? yes | ||
## Enter the job numbers | ## Enter the job numbers | ||
## Check the different sites: | ## Check the different sites: | ||
### http://download.eclipse.org/modeling/mdt/papyrus/updates/milestones/1.1/RC3/?d | ### http://download.eclipse.org/modeling/mdt/papyrus/updates/milestones/1.1/RC3/?d | ||
### https://www.eclipse.org/papyrus/downloads/ | ### https://www.eclipse.org/papyrus/downloads/ |
Revision as of 10:13, 3 June 2015
Contents
Comment
- @improvement create a bugzilla first
- @improvment create a query to find all repositories to be updated manually
- @bug the automatic repository version updater seems to introduce non unix break lines
- @improvment define the list of user able to execute a build on papyrus master
Overview
- one week before setup a team: at least one commiter with one other personn
- one day before send an email to the mailing
- release day send an email to the papyrus developer mailing list before the release
- make the release
- release day send an email to the papyrus developer mailing list after the release
- release day send an email to the cross project mailing list after the release
Email template proposal
- one week end before: XXXX
- release day initial email: Hi everyone !Today is build day so if you can refrain yourselves from pushing troublesome features we would greatly appreciate it.Papyrus Core Team
Prerequisite
- fresh eclipse <version> nightly Eclipse for RCP and RAP Developers
- papyrus project in workspace: git new branch on master synchro with the master branch with releng project imported
- simrel project in workspace: git://git.eclipse.org/gitroot/simrel/org.eclipse.simrel.build.git
Release Plan Action
- Update dependencies from Agregation Build Models
- Help>Install> Update site: https://hudson.eclipse.org/papyrus/view/Mars/job/Papyrus-Master-Developer/lastSuccessfulBuild/artifact/releng/dev/target/repository/
- right click on the *.pom.xml and oomph papyrus.setup
- /releng/org.eclipse.papyrus.oomph/setups/papyrus.setup
- /releng/top-pom-dev.xml
- /releng/top-pom-extra-tests.xml
- /releng/top-pom-extras.xml
- /releng/top-pom-main-tests.xml
- /releng/top-pom-main.xml
- /releng/top-pom-rcp.xml
- Selection the right version and check the Confirmation Location Update, each version should be the lastest official version except if you depend on a specific build version, unreleased officially
- Update dependencies manually
- for all unannotated repositories,
- @missing cmd: find . -name "top-pom*" | xargs -t -i grep "manualUpdate" -b1 {}
- for detection of manual repository example repository orbit find the lastest url http://download.eclipse.org/tools/orbit/downloads/
- Tag the new version in the git repository
- Deploy the new version
- Push on Papyrus gerrit
- tag to be used [Releng] Update dependencies for <Eclipse Version> <Milestone>
- Execute the Papyrus-Master hudson job with the new parameters with no sign
- Go: https://hudson.eclipse.org/papyrus/view/Mars/job/Papyrus-Master/
- Add parameters
- BUILD_ALIAS : the name of the release (0.9.0, 1.1.0M6, etc.); leave it blank for nightly and integration builds
- SIGN : whether to sign the update site (can take up to an hour on the Eclipse build server); mandatory for all builds except nightlies
- last 15 mn
- In parrallele Execute the Papyrus-Master hudson job with the new parameters with sign
- Go: https://hudson.eclipse.org/papyrus/view/Mars/job/Papyrus-Master/
- Add parameters
- BUILD_ALIAS : the name of the release (0.9.0, 1.1.0M6, etc.); leave it blank for nightly and integration builds
- SIGN : whether to sign the update site (can take up to an hour on the Eclipse build server); mandatory for all builds except nightlies
- last 1 hour
- Automatically execute the Papyrus-Master-Test hudson job
- Execute the Papyrus-Master-Extra hudson job with the new parameter with sign
- Go: https://hudson.eclipse.org/papyrus/view/Mars/job/Papyrus-Master-Extra/
- Add parameters
- SIGN : whether to sign the update site (can take up to an hour on the Eclipse build server); mandatory for all builds except nightlies
- last 1 hour
- Push on Papyrus gerrit
- Keep the hudson job for MASTER and MASTER-EXTRA, the one that have been tagged and sign
- Execute the publication
With the script
To publish a milestone or release from a build, you can use the manualPromote.sh for Luna, and manualPromote-mars.sh for Mars, script on: /opt/public/modeling/mdt/papyrus/manualPromote.sh Start this script, and fill in the parameters in the interactive script.
For example:
$ cd /opt/public/modeling/mdt/papyrus/ $ ./manualPromote.sh -------------------- user parameters -------------------- mainBuildNumber (the number of the "papyrus-trunk-nightly" Hudson build from which to publish the main Papyrus plug-ins): ? 519 extrasBuildNumber (the number of the "papyrus-trunk-extra-nightly" Hudson build from which to publish the extra Papyrus plug-ins, or 0 to not publish): ? 43 testsBuildNumber (the number of the "papyrus-trunk-nightly-tests" Hudson build from which to publish the test results, or 0 to not publish): ? 93 version (e.g. "0.9.0"): ? 0.9.0 updateSite (e.g. "nightly/juno", "milestones/0.9/M5", "releases/indigo/0.8.1") : ? milestones/0.9/M5 Are you sure you want to publish with these parameters (yes|no)? ? yes
- Enter the job numbers
- Check the different sites: