Closed Bug 1253366 Opened 4 years ago Closed 4 years ago

Set up second prod release runner instance based on default

Categories

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

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

Attachments

(1 file)

It'd be great to set up another release runner instance which will be used as a production instance for release promotion releases, so we can continue using the dev instance for dev.
Comment on attachment 8726903 [details]
MozReview Request: Bug 1253366 - Set up second prod release runner instance based on default r=jlund

https://reviewboard.mozilla.org/r/38299/#review34933

oh wow. that's nice. grepping puppet suggests it doesn't know about 'old-release-runner'. I guess that's a manual hack directly on the current prod node?
Attachment #8726903 - Flags: review?(jlund) → review+
(In reply to Jordan Lund (:jlund) from comment #2)
> oh wow. that's nice. grepping puppet suggests it doesn't know about
> 'old-release-runner'. I guess that's a manual hack directly on the current
> prod node?

Yeah, the branch is used only as a part of initial setup.
Assignee: nobody → rail
Comment on attachment 8726903 [details]
MozReview Request: Bug 1253366 - Set up second prod release runner instance based on default r=jlund

https://hg.mozilla.org/build/puppet/rev/b6ea640db09b
Attachment #8726903 - Flags: checked-in+
Just checked, it's up!
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.