1332341 - [tracking] Use balrogworker-v1 in release promotion

Status: RESOLVED FIXED

(Release Engineering :: Release Automation, defect, P1)

Description

[Rail Aliiev [:rail]]

This way we can get rid of using regular TC workers with balrogVPN feature enabled and avoid passing encrypted credentials.

Comment 1

[Greg Arndt [:garndt]]

Do we know if this will be something completed in Q2?

Comment 2

[Rail Aliiev [:rail]]

TBH, I doubt about Q2, because we haven't even started looking at this yet. It looks like this will require us to switch to in-tree scheduling, because balrogworker-v1 requires CoT. We have been thinking about this (the scheduling part) as a project for the intern starting next week.

Comment 4

[Rail Aliiev [:rail]]

Attachment: balrogscript.partials.diff

I haven't tested this patch, but it should give you an idea how to add this behaviour.

Also see https://bugzilla.mozilla.org/show_bug.cgi?id=1413149#c7

Comment 5

[Mihai Tabara [:mtabara]⌚️GMT]

Let's track separately the stuff we need to get done in order to see this going forward:

* we need balrogscript changes to enable release-behavior
* we need to tweak beetmoverscript to tweak the manifest in order to supply the release information too
* we need to add in-tree balrog jobs to enable the actual tasks on maple

Comment 6

[Mihai Tabara [:mtabara]⌚️GMT]

It gives me great satisfaction to close this bug with fire!