[jbosstools-issues] [JBoss JIRA] (JBIDE-11512) Create a script or sthg like that to create new "branch" jobs from trunk.

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683421#comment-12683421 ] 

Mickael Istria commented on JBIDE-11512:
----------------------------------------

The issue is that there can be huge differences between stable_branch and trunk. For example, we added tests in trunk and configured hudson jobs consequently. Hudson jobs maintenance is synchronized with code maintenance, and code maintenance is using branch.
Maintaining an alternative approach such as the one we have currently is less clear and make daily maintenance more difficult and less clear (need to apply changes on branch all the time although modification is not part of previous branch roadmap/tasks).
It seems like creating a new view by copying DevStudio_Trunk into DevStudio_3.3.Beta3 wouldn't be much more work than applying changes you suggested; and it would allow us to be synchronized with the code we build and prevent us from having to backport useless changes into "Stable_Branch".

For any structural change happens between Stable_Branch and BetaN+1 (let's say a move to Git for example), then we need to do the work twice since we cannot backport this structural change. Whereas following the same "pattern" as for development using branches, we are sure we'll never encouter this issue.
                
> 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