1561934 - Please clone comm-beta to releases/comm-esr68

Status: RESOLVED FIXED

(Developer Services :: Mercurial: hg.mozilla.org, task)

Description

[Rob Lemley [:rjl]]

Please clone the default branch of comm-beta to releases/comm-esr68. The configuration should be the same as comm-esr60.
The earliest we'll need it is merge day on 7/8.
Thanks

Comment 1

[Connor Sheehan [:sheehan]]

I will kick this off this afternoon.

Bug 1555777 contains similar work done for esr68.

Comment 2

[Connor Sheehan [:sheehan]]

Attachment: hgwsgi: add `comm-esr68` (Bug 1561934) r?smacleod

The repo is already cloned on-disk, this will make it available
over http.

Comment 3

[Connor Sheehan [:sheehan]]

Attachment: mozautomation: add `comm-esr68` (Bug 1561934) r?smacleod

Comment 4

[Connor Sheehan [:sheehan]]

Attachment: ansible/hg-web: add `comm-esr68` to replicationrules (Bug 1561934) r?smacleod

This will make the hgweb mirrors in AWS take action on events
for the new repo. The rule has already been manually set on
the mirrors to allow the initial clone to replicate.

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/a98a675f7ba9
hgwsgi: add comm-esr68 r=smacleod
https://hg.mozilla.org/hgcustom/version-control-tools/rev/e1f492423b17
mozautomation: add comm-esr68 r=smacleod
https://hg.mozilla.org/hgcustom/version-control-tools/rev/9a457bdd76d2
ansible/hg-web: add comm-esr68 to replicationrules r=smacleod

Comment 6

[Connor Sheehan [:sheehan]]

Landed all the patches and created the repo, but I still need to deploy this.

Comment 7

[Jorg K (CEST = GMT+2)]

Yes, like https://hg.mozilla.org/releases/comm-esr68/ doesn't work right now. What about a treeherder - https://treeherder.mozilla.org/#/jobs?repo=comm-esr68?

Comment 8

[Connor Sheehan [:sheehan]]

(In reply to Jorg K (GMT+2) from comment #7)

Yes, like https://hg.mozilla.org/releases/comm-esr68/ doesn't work right now. What about a treeherder - https://treeherder.mozilla.org/#/jobs?repo=comm-esr68?

It will show up after the deploy, which I have just kicked off. I've set the required Treeherder variable in the hgrc, but you may need to coordinate with Treeherder to get CI running (I'm not actually sure).

Comment 9

[Rob Lemley [:rjl]]

Attachment: Bug 1561934 - Add comm-esr68 repository; r?tomprince

Repository is already set up.

Comment 10

[GitHub Bugzilla PR Linker]

Attachment: Link to GitHub pull-request: https://github.com/mozilla/treeherder/pull/5134

Comment 11

[Patrick Cloke [:clokep]]

When trying to push to comm-esr68 today I get the following:

pushing to ssh://hg.mozilla.org/releases/comm-esr68
searching for changes
remote: abort: could not lock working directory of /repo/hg/mozilla/releases/comm-esr68: Permission denied                                                      
abort: stream ended unexpectedly (got 0 bytes, expected 4)

Talked to Tom Prince on IRC and he suggested:

I bet it doesn't have the proper owner. clokep: I'd ni sh.eehan on the creation bug with that error

Thanks in advance!

Comment 12

[Connor Sheehan [:sheehan]]

I doubled checked the permissions and they seem to be in order. Just to be safe I ran the permission setting script, and it did change the mode on some files. Try again and see if that helped (though I doubt it would have mattered).

I'd say it's more likely you have lost your push privileges on hg.mo due to inactivity. Try directly SSH'ing in to hg.mozilla.org and making sure you are able to push to scm_level_3 repositories (something like ssh [e-mail]@hg.mozilla.org -i <path to your key>). If you don't have the permissions any more, you need to file a bug to have them re-instated. Usually it's quite quick turnaround as long as you've had scm_level_3 at some point in the recent past.

Comment 13

[Jorg K (CEST = GMT+2)]

Patrick pushed to C-C and C-B as part of the merges, so his privileges worked yesterday :-)

Comment 14

[Connor Sheehan [:sheehan]]

(In reply to Jorg K (GMT+2) from comment #13)

Patrick pushed to C-C and C-B as part of the merges, so his privileges worked yesterday :-)

Hmmmm in that case, it probably was those files with bad modes. Try pushing again and let me know if you still can't get through. :)

Comment 15

[Patrick Cloke [:clokep]]

I just pushed again and it worked fine, so seems like it was a bad file permission. Thanks for taking care of this!

Comment 16

[Rob Lemley [:rjl]]

Attachment: Bug 1561934 - Set grants for comm-esr68 to match comm-esr60. r?tomprince