We have several issues with builds that have an AUS/Balrog component failing. Several were disabled in November and more will be disabled soon. This bug is for creating a generic AUS task that can be used as a consistent interface to balrog. A docker image with the necessary config and/or credentials is also needed. A few options exist: * using a private docker image * using a public docker image with encrypted secrets * using a public docker image, deployed in a VPC that has access to AUS Use of this task probably should be constrained by a set of scopes administrated by RelEng.
After talking with Selena who talked with Rail... and I ended up talking to Rail as well... I think if funsize image was moved over, we could just use the image to set up the tasks? Marking bug 1217130 as a blocker, if I'm wrong please undo.
Depends on: 1217130
See Also: → bug 1244893
I don't think this depends on putting funsize images into the tree.
No longer depends on: 1217130
There isn't a hard dependency on bug 1245837, but my current approach will involve fixing that bug first.
Depends on: 1245837
Most likely I'm going to be focused on signing with the new worker lib, and this bug will be for someone else.
catlee: is this the piece we're considering having Ben mentor Varun with?
I'm not sure that Varun will be able to get to it if we're aiming for mid-Q2. When do we think we need this by?
I'd like to get my hands dirty on this bug as it seems to block a bunch of other people's work. @Aki: * in the lights of MozLondon conversations and direction shifts, is this something we want in the current form or are there any new ideas to take into consideration? * with respect to the options selena mentioned in the description, is there a preferred one I should consider? I'm trying to enrich the context here so any other piece of information is appreciated. Thanks!
This would probably be a great use of scriptworker, where that scriptworker runs somewhere with network access to balrog.
This is scriptworker, which isn't finished (needs chain of trust support) but is usable. I think that's enough to resolve this bug.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
Hm, the generic tool is scriptworker, but it doesn't handle balrog atm. This should be open for the script portion of balrog.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
:mtabara - :fkang is working on balrog-in-scriptworker; maybe talk with him to make sure you're not duplicating effort?
Thanks for the heads-up Aki! I've got my hands dirty in some other stuff this week but I'll double check with :fkang before I'll jump back here. Thanks again for the update
Francis is working on this in bug 1277871 now, so this is effectively a dupe.
Status: REOPENED → RESOLVED
Last Resolved: 2 years ago → 2 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1277871
You need to log in before you can comment on or make changes to this bug.