[
https://issues.jboss.org/browse/JBIDE-11512?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11512:
------------------------------------
Your above workflow is only needed when it's time to branch for the FIRST MILESTONE on
a stream, eg., we'll need this for the JBT 3.4M1 / JBDS6.0M1 builds. Otherwise the
existing stable_branch jobs can simply be edited and reused as you move from branch to
branch through a stream, because let's be real, you'll NEVER have to rebuild
something from, for example, the M5 branch using the current stable_branch job. We only
move forward, not sideways.
I agree however that when it's time for the first milestone, you DO need a new view,
series of jobs cloned from trunk, updated cascade docs [1], and so forth.
[1]
http://download.jboss.org/jbosstools/builds/cascade/3.3.indigo.html
I also agree that migrating the old version of a stable_branch job to is newer equivalent
is a bit tedious. I'm just not convinced that creating new jobs and destroying old
ones is the way to go, because changing job names every 6 weeks is a royal pain in the ass
from a maintenance POV and means you have to ensure all your composite sites are properly
config'd thereafter.
If you can simply generate jobs based on trunk, why not generate them using the same names
as existant, and push them to the server using my hudpull/hudpush pair? Related... I wrote
a mojo [1] to do this based on a template, but if could be adjusted to work using regex
replacements, eg., job foo_trunk -> foo_stable_branch and uses svn repo in trunk ->
branches/3.3.0.some.milestone, etc.
[1]
https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-publish...
Create a script or sthg like that to create new "branch"
jobs from trunk.
-------------------------------------------------------------------------
Key: JBIDE-11512
URL:
https://issues.jboss.org/browse/JBIDE-11512
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Minor
Fix For: 3.3.0.Beta3
In Jenkins,
Since betaX is a fork from trunk, it would be more convenient to find a way to create the
betaX jobs and view as a fork of Trunk jobs. It would prevent from having to backport
stuff all the time, and would make the jobs follow the same logic as code.
Please list there the technical issues that this script will have to deal with.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira