1283640 - Migrate deployment code for build-release-kickoff

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Hal Wine [:hwine] use NI!]

bug 1277443 comment 7 missed the issue that the app deploys from git.mozilla.org via chief. The deployment must be fixed before we can disable writes to the repo.

Comment 1

[Jonathan Griffin (:jgriffin)]

(In reply to Hal Wine [:hwine] (use NI) from comment #0)
> bug 1277443 comment 7 missed the issue that the app deploys from
> git.mozilla.org via chief. The deployment must be fixed before we can
> disable writes to the repo.

Who owns updating this? We'd like to turn off git.m.o next week.

Comment 2

[Hal Wine [:hwine] use NI!]

(In reply to Jonathan Griffin (:jgriffin) from comment #1)
> Who owns updating this? We'd like to turn off git.m.o next week.

Punting prioritization to :catlee -- aiui, this will need cross team coordination:
 - someone from releng who knows the app requirements
 - someone from webops who can make the enhancements on their side

Depending on the scope of webops work, resources may not be available until after mid July without escalation.

Based on results yesterday, git.m.o is required for release-kickoff change deployment.

Comment 3

[Rail Aliiev [:rail]]

(In reply to Hal Wine [:hwine] (use NI) from comment #2)
>  - someone from releng who knows the app requirements

I can help with this.

Comment 4

[Nick Thomas [:nthomas] (UTC+12)]

rail, what's involved with this ? A first guess was 'just' WebOps changing chief to point to a new origin.

Comment 5

[Rail Aliiev [:rail]]

(In reply to Nick Thomas [:nthomas] from comment #4)
> rail, what's involved with this ? A first guess was 'just' WebOps changing
> chief to point to a new origin.

That should work just fine.

Probably it's not a good idea to reinvent a new home for the current version of ship-it. v2 will be perfect! :)

Comment 6

[Jonathan Griffin (:jgriffin)]

(In reply to Rail Aliiev [:rail] from comment #5)
> (In reply to Nick Thomas [:nthomas] from comment #4)
> > rail, what's involved with this ? A first guess was 'just' WebOps changing
> > chief to point to a new origin.
> 
> That should work just fine.
> 
> Probably it's not a good idea to reinvent a new home for the current version
> of ship-it. v2 will be perfect! 

Rail, have you reached out to WebOps yet, and if not, what action needs to happen?

Comment 7

[Rail Aliiev [:rail]]

Ooops, sorry, I misunderstood something. Let's ask fox2mike! :)

Shyam, we want to use github.com instead of git.m.o in chief for ship-it (http://genericadm.private.phx1.mozilla.com/chief/shipit.prod and http://genericadm.private.phx1.mozilla.com/chief/shipit.stage). How easy it would be to switch to github.com?

Comment 8

[Rail Aliiev [:rail]]

FTR, the new URL is https://github.com/mozilla/ship-it/

Comment 9

[Hal Wine [:hwine] use NI!]

(In reply to Rail Aliiev [:rail] from comment #8)
> FTR, the new URL is https://github.com/mozilla/ship-it/

Correction: the new URL will be https://github.com/mozilla-releng/ship-it

I'll update when that is active (later today)
[also clearing ni on :catlee]

Comment 10

[Hal Wine [:hwine] use NI!]

(In reply to Hal Wine [:hwine] (use NI) from comment #9)
> (In reply to Rail Aliiev [:rail] from comment #8)
> > FTR, the new URL is https://github.com/mozilla/ship-it/
> 
> Correction: the new URL will be https://github.com/mozilla-releng/ship-it

Repo live at: https://github.com/mozilla-releng/ship-it.git

Comment 11

[Shyam Mani [:fox2mike]]

(In reply to Rail Aliiev [:rail] from comment #7)
> Ooops, sorry, I misunderstood something. Let's ask fox2mike! :)
> 
> Shyam, we want to use github.com instead of git.m.o in chief for ship-it
> (http://genericadm.private.phx1.mozilla.com/chief/shipit.prod and
> http://genericadm.private.phx1.mozilla.com/chief/shipit.stage). How easy it
> would be to switch to github.com?

I'm not entirely sure, but it shouldn't be too complex. We'll track the work in Bug 1285319, so it'll be something we can follow along there. Thanks!

Comment 12

[Jonathan Griffin (:jgriffin)]

Can this bug be closed? It looks like WebOps made the necessary changes in bug 1285319.

Comment 13

[Hal Wine [:hwine] use NI!]

302 :rail -- I have no way to verify proper operation.

Comment 14

[Rail Aliiev [:rail]]

All good, just deployed. \o/