[jbossts-issues] [JBoss JIRA] (JBTM-1251) Create EAP7 jobs in hudson

[Paul Robinson (JIRA)]

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

Paul Robinson commented on JBTM-1251:
-------------------------------------

You don't need to branch the quickstart, narayana, or docs branches to create these jobs. Currently 5.x and 4.17 share a common branch (master) so both sets of jobs build against master. The place in which they differ is that 4.17 builds against 4_BRANCH of our jboss-as fork and 5.x against 5_BRANCH. They also differ in what is tested as TXF is only tested in 5.x. 

I would suggest we create the jobs now, but the problem is that we are going to double the load on Hudson as any change is going to trigger both the EAP61 and the narayana-500 version of the job.

The reason why I'm keen to get some narayana 5.x CI is that TXF is currently not getting any CI. Maybe I could just create some TXF jobs in the mean time until this is resolved?
                
> Create EAP7 jobs in hudson
> --------------------------
>
>                 Key: JBTM-1251
>                 URL: https://issues.jboss.org/browse/JBTM-1251
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Testing
>            Reporter: Paul Robinson
>            Assignee: Tom Jenkinson
>             Fix For: 5.0.0.M2
>
>
> Currently we have a set of narayana-* jobs that are targeted at EAP6. These build against the 4_BRANCH of our jbossas fork. Narayana 5.x is targeted at EAP7 and the 5_BRANCH of our jbossas fork. We therefore need to:
> rename all narayana* to narayana-EAP6*
> rename all btny-quickstarts-* to btny-EAP6-quickstarts- (or similar)
> clone all narayana-EAP6 and btny-EAP6-quickstarts- jobs to create EAP7 variants that build against the 4_BRANCH of our jbossas fork.

--
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