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

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Mon Sep 17 03:54:34 EDT 2012

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

Tom Jenkinson commented on JBTM-1251:

In an ideal world you would have a branch as TXF qs src wouldn't be in the 4.17 branch (there is a precedent for leaving unsupported code in the main project, I would ideally not have that be the case in the documentation pack). As you say, you should be able to set the jobs up now, the slight issue being immediately prior to release of 4.17 they may break briefly as we move the TXF docs related (of which I include qs) stuff out of the way for tagging.

I have moved the existing jobs to be named jbossts-EAP61-branch417.

I think the community version should maybe track AS instead of EAP. Therefore I think call it narayana-500-AS72 - note I am going to rename all jobs to be consistent with that, i.e. jbossts-EAP61-branch417 will move to jbossts-branch417-EAP61
> 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

More information about the jbossts-issues mailing list