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.
EMF Compare/Build
< EMF Compare
Revision as of 04:36, 14 May 2013 by Laurent.goubet.obeo.fr (Talk | contribs) (New page: = Build job locations = '''The latest version can always be built with the ''Master'' job.''' The current master contains version 2.1.*. * Master : https://hudson.eclipse.org/hudson/view...)
Build job locations
The latest version can always be built with the Master job. The current master contains version 2.1.*.
- Master : https://hudson.eclipse.org/hudson/view/Modeling/job/emf-compare-master/
- 1.3.* : https://hudson.eclipse.org/hudson/view/Modeling/job/emf-compare-1.3/
- 1.2.* : https://hudson.eclipse.org/hudson/view/Modeling/job/emf-compare-1.2.0/
- 1.1.* : https://hudson.eclipse.org/hudson/view/Modeling/job/emf-compare-1.1/
Launching a Build
Members of the EMF Compare team are the only persons that can launch builds. You will need to be connected to hudson and on the page of the job you want to run (see above).
There are four parameters to a build :
- Type
- N => Nightly. Unstable builds that won't be tested in-depth and are not meant to be largely distributed. One is launched every night.
- I => Integration. Should be used for builds that are meant to be tested by users, for example if a build has been launched to fix a given bug which resolution must still be verified.
- M => Maintenance. Not used by EMF Compare.
- S => Stable. Should be used for every Milestone or Release Candidate (RC) builds.
- R => Release. Must never be used from hudson. The "R" or "Release" version is in fact a renaming of the latest "Stable" RC build; refer to the promotion instructions below.
- Alias
- Must always be filled for "S" type builds. The alias format must follow the rule <major>.<minor>.<micro><build alias>. For example, when building the M7 milestone of version 2.1.0, the alias must be filled to "2.1.0M7" or to "2.1.0RC2" when building the second release candidate.
- Sign
- Mandatory for all "S" type builds. This can be left unchecked for N and I builds.
- Platform
- Kepler => Default platform at the time of writing. This will mean that the build must be run with Kepler (Eclipse 4.3) dependencies.
- Juno => If the build must be run against Juno (Eclipse 4.2) dependencies.
- Indigo => For builds that need Indigo (Eclipse 3.7) dependencies.
Promotion Instructions
Note that you need access rights on build.eclipse.org so that you can connect via ssh build.eclipse.org. If you need to promote a build but lack a shell access, open a bug such as 386379 to request an unrestricted shell access explaining "why" you need it.
For all builds
- Launch build on the required hudson job. Let's assume here that you build the latest version through job emf-compare-master.
- Once the build has passed
- Connect to build.eclipse.org (ssh build.eclipse.org)
- Go to the appropriate folder for promotion (here, cd /shared/jobs/emf-compare-master/lastSuccessful/archive/packaging/org.eclipse.emf.compare.update/target/promotion/, replace the job name accordingly)
- Launch the promoter (ant -f promoter.xml)
- Keep the build qualifier in mind, it will be indicated in the promoter log (for example, 201303191750 was the qualifier of our 2.1.0M6)