[
https://issues.jboss.org/browse/JBIDE-21381?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-21381:
------------------------------------
There's also a bucket of beaker slaves [7], which are a mix of RHEL6 [8] and 7 [9],
with a few ppc slaves [10] and one that's only a "beaker" slave with no
additional qualifiers [11.
[7]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/beaker/ (30 enabled, 9
disabled)
[8]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/beaker&&RHEL6/ (12
enabled, 4 disabled)
[9]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/beaker&&EAP... (14
enabled, 2 disabled)
[10]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/beaker&&ppc64/ (4
enabled, 2 disabled)
[11]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/brms06-rhel6-x86...
So, I think for component & aggregate builds on RHEL6/7 we want something like this,
including the beaker slaves:
*
(RHEL7-ipv6||brms-rhel7-x86-64||beaker-fsw-rhel7||EAP-RHEL7||RHEL6||jboss-prod||beaker)&&!ia64&&!ppc64&&!rhts
=
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/%28RHEL7-ipv6||brms...
And for more restrictive jobs like the install jobs, we want something like this,
excluding the beaker slaves:
*
(RHEL7-ipv6||brms-rhel7-x86-64||beaker-fsw-rhel7||EAP-RHEL7||RHEL6||jboss-prod)&&!beaker&&!ia64&&!ppc64&&!rhts
=
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/%28RHEL7-ipv6||brms...
Ensure JBT/JBDS are building on RHEL 7 slaves where applicable
--------------------------------------------------------------
Key: JBIDE-21381
URL:
https://issues.jboss.org/browse/JBIDE-21381
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
We currently use an *<assignedNode>* or *label_exp* like this for most of our
jobs:
* (RHEL6||RHEL7||jboss-prod)&&!ia64&&!rhts
* (RHEL6||jboss-prod)&&!ia64&&!ppc64&&!rhts
* (RHEL6||RHEL7||jboss-prod)&&(x86||x86_64)
However, there are currently no slaves in the RHEL7 label [0], so this query really just
means RHEL6||jboss-prod.
[0]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/RHEL7/
But, since the jboss-prod slaves do NOT have x86 or x86_64 labels, using
jboss-prod&&(x86||x86_64) also means ZERO slaves [1].
[1]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/%28jboss-prod%29&am...
Therefore (RHEL6||RHEL7||jboss-prod)&&(x86||x86_64) ==
RHEL6&&(x86||x86_64) == RHEL6.
And, jboss-prod only includes RHEL6 slaves [2]:
[2]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/jboss-prod/
Here's a label query which actually includes some RHEL7 slaves, from the RHEL7-ipv6
bucket of THREE slaves [3]:
[3]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/RHEL7-ipv6/
Note too that there are no longer any rhts slaves [4], but there are still some ia64 [5]
and ppc64 [6] slaves:
[4]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/rhts/
[5]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/ia64/
[6]
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/ppc64/
So... if we want a pool of >60 of RHEL6||jboss-prod and also RHEL7-ipv6 (all three of
them), we can use these slaves from *(RHEL6||RHEL7-ipv6||jboss-prod)*:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/%28RHEL6||RHEL7-ipv...
There are also some unshared RHEL7 slaves we can use:
*
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/brms-rhel7-x86-64/ (5 disabled)
*
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/beaker-fsw-rhel7/ (4 disabled)
*
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/EAP-RHEL7/ (14 enabled, 2
disabled)
So, here's the combined RHEL7 label:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/brms-rhel7-x86-64||...
(17 enabled, 11 disabled)
And the combined RHEL6 label:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/%28RHEL6||jboss-pro... (60
enabled, 4 disabled)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)