[jbossts-issues] [JBoss JIRA] (JBTM-1463) Allow pull requests to test pull requests for the jbosstm fork of jboss-as

Tom Jenkinson (JIRA) jira-events at lists.jboss.org
Thu Feb 7 11:07:51 EST 2013

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

Tom Jenkinson commented on JBTM-1463:

you are right in your concern and that is what I am trying to address but ineloquently

I was thinking more about changes to narayana that need a change to jbosstm somehow being able to test both pulls at once.

Maybe we could somehow put convention when you raise a pull request for jbosstm that you can put a comment to say something like:

"requires: https://github.com/jbosstm/jboss-as/pull/217"

We can then somehow use that info in the narayana.sh to pull in that branch rather than 5_BRANCH, what do you think? I know you did some work with using rest to talk to git hub to comment on pulls, could it possibly download the comment for the pull in order to grep it for that info?

> Allow pull requests to test pull requests for the jbosstm fork of jboss-as
> --------------------------------------------------------------------------
>                 Key: JBTM-1463
>                 URL: https://issues.jboss.org/browse/JBTM-1463
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Build System
>            Reporter: Tom Jenkinson
>            Assignee: Paul Robinson
>             Fix For: 5.0.0.Final
> to allow changes to our repo and to pull in changes we need to AS7 but not require those changes to be pushed to 5_BRANCH until they are tested

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