496367 - Hg Account Request for SeaMonkey Release Automation - user seabld

Status: VERIFIED FIXED

(mozilla.org :: Repository Account Requests, task)

Description

[Robert Kaiser]

Attachment: seabld_dsa.pub (public SSH key)

For enabling the SeaMonkey release automation to do relbranching and tagging, we need Mercurial access, including access to mozilla-central/-1.9.1, comm-central and L10n repos, for the seabld user that is used by the SeaMonkey buildbots.

The same user with the same key has access to stage, aus2-community and the symbol push server, so it's been an established user/key for build stuff for a long time now.

I'm attaching the seabld_dsa.pub file we have in use on all those boxes.

Comment 1

[Robert Kaiser]

Any chance we can forward with this?

What steps do I need to take care about?

It's hard to apply the usual commit access rules for a build&release account, the key itself might be everything we can reasonably require/provide here.

This blocks not only future SeaMonkey releases, it also blocks testing the release automation harness work I'm trying to do right now so that we can drive SeaMonkey releases with the same harness as Firefox ones.

Comment 2

[Reed Loden [:reed]]

Yeah, sounds fine to me, as we've done the same thing for Firefox and Thunderbird (and maybe others).

Comment 3

[Robert Kaiser]

BTW, when you're at it, could you check if seabld has cvs access as well? Unfortunately, we still have ChatZilla on cvs and need to tag it for releases as well.

Comment 4

[Robert Kaiser]

I just checked, please enable commit access for seabld to CVS as well, currently it gets this warning:

The seabld account is not permitted to check-in to this CVS repository.
If you think it should be allowed to do so, please contact
the system administrators at [e-mail].

Comment 5

[[e-mail] (:bhearsum)]

FWIW, we don't have similar CVS access for ffxbld. You can disable the checking in of the patcher config with one of the parameters to ReleaseUpdatesFactory, http://hg.mozilla.org/build/buildbotcustom/file/tip/process/factory.py#l1791.

Comment 6

[Robert Kaiser]

(In reply to comment #5)
> FWIW, we don't have similar CVS access for ffxbld. You can disable the checking
> in of the patcher config with one of the parameters to ReleaseUpdatesFactory,
> http://hg.mozilla.org/build/buildbotcustom/file/tip/process/factory.py#l1791.

But I can't avoid tagging ChatZilla, which is a part of our SeaMonkey releases and still hosted on CVS :(
And don't you use the cltbld account for checking in patcher configs?

Comment 7

[[e-mail] (:bhearsum)]

(In reply to comment #6)
> (In reply to comment #5)
> > FWIW, we don't have similar CVS access for ffxbld. You can disable the checking
> > in of the patcher config with one of the parameters to ReleaseUpdatesFactory,
> > http://hg.mozilla.org/build/buildbotcustom/file/tip/process/factory.py#l1791.
> 
> But I can't avoid tagging ChatZilla, which is a part of our SeaMonkey releases
> and still hosted on CVS :(
> And don't you use the cltbld account for checking in patcher configs?

Yes, in production. Sorry, I thought this bug was about a staging seabld account for some reason - please ignore me!

Comment 8

[Reed Loden [:reed]]

Done for both Hg and CVS.

Comment 9

[Robert Kaiser]

verified, I can play with personal hg repos and check into cvs. Didn't test pushing to official mozilla-* and comm-central repos, but I take it that this works. Will see when pushing the first release tags.