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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-11512:
------------------------------------

we already have 40+ stable_branch jobs. All that's needed to bump them from Beta1 SVN branch to Beta3 branch is to:

1. pull down the latest versions from Jenkins (using 'hudpull' script), 
2. do a global find and replace on the config.xml files, 

s#Beta1#Beta3#g
s#<disabled>true</disabled>#<disabled>false</disabled>#g

3. push changes to the server (using 'hudpush' script)
4. commit changed config.xml files to SVN 

For generating jobs from a template, (eg., the FIRST time we branch on a new stream, like when we start JBDS 6.0M1 and need to spawn 40 new jobs from trunk) there's this:

https://github.com/nickboldt/maven-plugins/tree/master/hudson-job-publisher-plugin

                
> 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