[jbosstools-issues] [JBoss JIRA] (JBDS-1931) evaluate Jenkins slave use for JBDS/JBT build jobs
[
https://issues.jboss.org/browse/JBDS-1931?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-1931 at 11/16/11 7:05 PM:
------------------------------------------------------------
Depends on rollout of new label scheme, JBQA-4222.
Ref: http://post-office.corp.redhat.com/archives/jbds-pm-list/2011-November/ms...
was (Author: nickboldt):
Depends on rollout of new label scheme.
Ref: http://post-office.corp.redhat.com/archives/jbds-pm-list/2011-November/ms...
evaluate Jenkins slave use for JBDS/JBT build jobs
--------------------------------------------------
Key: JBDS-1931
URL: https://issues.jboss.org/browse/JBDS-1931
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.0.M5
Most jobs run on
{code}
<assignedNode>RHEL_any&&!RHEL4-ia64</assignedNode>
or
<assignedNode>RHEL5_any</assignedNode>
{code}
However, a few are still tied to either RHEL5_x86, RHEL5_x86_64, RHEL4_x86 or
RHEL4_x86_64.
And there's a new group of 5 slaves under RHEL6_x86_64 on which we could be building.
TODO:
1. fix jobs' assignedNodes
2. assign nodes to better labels (for example, there's no RHEL6_any and I don't
know if the 5 slaves in RHEL6_x86_64 are also included in RHEL_any).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira