Bug 1612655
Summary: | bugziller doesn't get an updated /opt/qa automatically | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Nigel Babu <nigelb> |
Component: | project-infrastructure | Assignee: | bugs <bugs> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | bugs, gluster-infra, mscherer |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-08-13 02:47:38 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nigel Babu
2018-08-06 05:13:56 UTC
So we can add it in the jenkins builder group, or we can split the opt/qa in a specific role. I guess the last one is the easiest and cleanest, as I am not looking at reviewing the role to see what side effect it could have on bugziller. Is it ok for you ? Done, I have added a role to extract on both bugziller. Can we start to switch to the internal one rather the external builder ? Yep, switching this one to its own role sounds best. We could switch over to the internal one. This looks like it is done. |