[ https://issues.jboss.org/browse/TOOLSDOC-359?page=com.atlassian.jira.plug... ] Nick Boldt commented on TOOLSDOC-359: ------------------------------------- Tweaking the job to source from 4.0.x branch is fine; in fact we can have TWO jobs... one for <=4.0.x [1] one for >=4.1 [2]. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs_40/ [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs_master/ and/or https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-docs_41/ Since each build would target a different folder on docs.jboss.org, I don't see a problem w/ them building in parallel from different source branches. I propose this mapping: * build from _master (master branch) ** --> http://docs.jboss.org/tools/nightly/trunk/ * build from _41 (latest stable branch, eg., jbosstools-4.1.0.Beta2x; eventually the jbosstools-4.1.x branch) ** --> http://docs.jboss.org/tools/nightly/4.1.kepler/ * build from _40 (jbosstools-4.0.x branch) ** --> http://docs.jboss.org/tools/4.0.1.Final/ (later, change job to target 4.0.2.Final, etc.) As to the question of need for a _master AND a _41 job, that depends on whether you need a split between "stabilizing doc in the Beta branch" and "raw doc in the master branch". If you do, you'll be following the same pattern that the developers use, and would branch presumably at the same time that they do for code freezes. If not, then you won't need a _41 branch until master becomes the branch for JBT 4.2 (and therefore you need a job to build from the 4.1.x branch, to allow for doc changes after 4.1.0.Final is released). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira