[
https://issues.jboss.org/browse/JBIDE-22630?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-22630:
------------------------------------
From eng-ops:
{quote}those particular slaves are owned/managed by EAP QE team. Those are provisioned
by the automation ([1]) which was taken over by EAP QE couple of months ago.
You can ask them for incorporation of your request to it or you can fix it by
yourself in [1], prepare PR and ask them for merge/rep-provision those slaves
after. I suppose all slaves under [2] are affected by this issue.
{code}
[1]
https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/mwqa-beaker-slav...
[2]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/label/EAP-RHEL7
bzira/jiralint fails often because of missing pip install
---------------------------------------------------------
Key: JBIDE-22630
URL:
https://issues.jboss.org/browse/JBIDE-22630
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Max Rydahl Andersen
bzia/jiralint oftenn fails because pip are missing from the servers it runs on.
shuold limit the nodes it runs on or get pip installed more generally.
error from build mails
{code}
+ pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz
Traceback (most recent call last):
File "/qa/services/hudson/.local/bin/pip", line 7, in <module>
from pip import main
ImportError: No module named pip
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)