Bugzilla – Full Text Bug Listing
| Summary: | Jobs for Emf Q/V/T | ||
|---|---|---|---|
| Product: | Community | Reporter: | Bernd Kolb <b.kolb> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | d_a_carver, nboldt |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Bernd Kolb
For ease of use (and to test a theory) I've created ONE job w/ a matrix of three subjobs for Q, V, and T. So, you can kick one process to cause all three builds to happen. Benefits: * a single CVS check will result in a rebuild of all three components; if query changes, you'll get a new transaction build (including the .qtv.all feature). * less places to go to kick a build by hand Costs: * if you only want to spin Transaction, you have to wait for the others to finish too * builds are run in parallel, rather than in series (this might be a problem) --- The alternative to the one-job-that-does-three-builds-in-parallel is three jobs which are chained together such that when Q is done, V runs; when V is done, T runs. You'd still get cvs-based on demand continuous builds *for each*, but you'd also get a cascade of serial builds instead of a matrix of parallel ones. --- You only need an extra job (or three, if I revert to one job per project rather than this matrix configuration) if you plan to run both N and I builds on a schedule, eg., N builds when needed and I builds every week at the same time. Milestones, RCs, and release builds can be done by hand via the Hudson interface. Click Build Now, then pass in new EXTRAFLAGS values such as -buildAlias 1.4.0.M5, and set the BUILDTYPE to the appropriate letter (S, R). In either scenario, you will need three boilerplate shell scripts, which I've assumed will be located in /cvsroot/modeling/org.eclipse.emf/org.eclipse.emf.${BUILDNAME}/releng/hudson/run.sh
Here's a sample script, with only two variables to set - projectid and version.
(These could be externalized as Hudson variables so you can change them there rather than in the script. If you like that idea, please open a bug in Dash > Common Builder).
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.dash/athena/org.eclipse.dash.commonbuilder/org.eclipse.dash.commonbuilder.releng/hudson/gef-3.5.x-nightly.sh?root=Technology_Project&revision=1.4&content-type=text%2Fplain
You all-in-one job is here:
https://build.eclipse.org/hudson/job/cbi-emf-qvt-1.4/
resolving as fixed. |