12:24 p.m.
Paul Robinson created JBTM-1251:
-----------------------------------
Summary: 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
4:09 p.m.
[
https://issues.jboss.org/browse/JBTM-1251?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1251:
-------------------------------------
Thanks for raising this Paul.
I would go with jbossts-EAP61-branch417 for the existing jobs.
We can never tell what the next EAP is, perhaps Narayana will fold into EAP8 or EAP6.x so
I am not sure of the naming for the future job though.
Maybe narayana-500 is OK (i.e. don't pin it to an EAP in terms of name)?
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
4:13 p.m.
[
https://issues.jboss.org/browse/JBTM-1251?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1251:
-------------------------------------
The question is when to add the Narayana quickstart jobs as they will require the
branching of its repo which is something I wanted to delay till after 4.17 is released.
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
1:36 a.m.
[
https://issues.jboss.org/browse/JBTM-1251?page=com.atlassian.jira.plugin....
]
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
2:54 a.m.
[
https://issues.jboss.org/browse/JBTM-1251?page=com.atlassian.jira.plugin....
]
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
3:10 a.m.
[
https://issues.jboss.org/browse/JBTM-1251?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on JBTM-1251:
-------------------------------------
I think we would need a branch/additional customization as scripts/hudson/narayana.sh has
a reference to 4_BRANCH in it. You need to externalize that into the job (I don't like
that as it is additional parameters to the script which is a kludge, or you need to
branch. You could have an optional environment variable too. i.e. if FOO not set
FOO=4_BRANCH git clone $FOO, then in the job you can set it to 5_BRANCH - up to you
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
8:53 a.m.
New subject: [JBoss JIRA] (JBTM-1251) Create narayana jobs in hudson
[
https://issues.jboss.org/browse/JBTM-1251?page=com.atlassian.jira.plugin....
]
Tom Jenkinson updated JBTM-1251:
--------------------------------
Summary: Create narayana jobs in hudson (was: Create EAP7 jobs in hudson)
Create narayana 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
9:26 a.m.
New subject: [JBoss JIRA] (JBTM-1251) Create narayana jobs in hudson
[
https://issues.jboss.org/browse/JBTM-1251?page=com.atlassian.jira.plugin....
]
Tom Jenkinson resolved JBTM-1251.
---------------------------------
Resolution: Done
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-AS-monitor/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-ipv6-dual...
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java6/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java7/
http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-skipTests/
http://172.17.131.2/view/Narayana+BlackTie/job/btny-narayana-documentation/
http://172.17.131.2/view/Narayana+BlackTie/job/btny-narayana-quickstarts/
Create narayana 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
4447
days inactive
4458
days old
jbossts-issues@lists.jboss.org
7 comments
2 participants
participants (2)
-
Paul Robinson (JIRA) -
Tom Jenkinson (JIRA)