1253366 - Set up second prod release runner instance based on default

Status: RESOLVED FIXED

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

Description

[Rail Aliiev [:rail]]

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 1

[Rail Aliiev [:rail]]

Attachment: MozReview Request: Bug 1253366 - Set up second prod release runner instance based on default r=jlund

Review commit: https://reviewboard.mozilla.org/r/38299/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/38299/

Comment 2

[Jordan Lund (:jlund)]

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?

Comment 3

[Rail Aliiev [:rail]]

(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.

Comment 4

[Rail Aliiev [: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

Comment 5

[Rail Aliiev [:rail]]

Just checked, it's up!