Bug 1612655 - bugziller doesn't get an updated /opt/qa automatically
Summary: bugziller doesn't get an updated /opt/qa automatically
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-06 05:13 UTC by Nigel Babu
Modified: 2018-08-13 02:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-13 02:47:38 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Nigel Babu 2018-08-06 05:13:56 UTC
I just realized that the bugziller machine isn't part of jenkins_builders. Which means we don't update /opt/qa for it with our nightly cron. Any change to the repo meant for this machine has to be done manually.

Let's solve this is it's automatic and less manual.

Comment 1 M. Scherer 2018-08-06 12:59:14 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 ?

Comment 2 M. Scherer 2018-08-06 14:57:21 UTC
Done, I have added a role to extract on both bugziller. Can we start to switch to the internal one rather the external builder ?

Comment 3 Nigel Babu 2018-08-07 09:11:58 UTC
Yep, switching this one to its own role sounds best. We could switch over to the internal one.

Comment 4 Nigel Babu 2018-08-13 02:47:38 UTC
This looks like it is done.


Note You need to log in before you can comment on or make changes to this bug.