Read-only CVS account for l10n builds

RESOLVED FIXED

Status

--
major
RESOLVED FIXED
11 years ago
4 years ago

People

(Reporter: Pike, Assigned: aravind)

Tracking

Details

Attachments

(1 attachment, 1 obsolete attachment)

(Reporter)

Description

11 years ago
For the l10n buildbot, I'd like to have a on-topic read-only cvs account like we have for other parts of our build automation.

Right now, it's pulling from cvs-mirror, which consistently drops check-ins. I could artificially lag the build logic, but that's not good in the long run.

It used to work for a while as the clock on l10n.m.o was skewed by about 10 minutes, now that reed has fixed that, I need to actually pick this part of the story up.

I generated a specific ssh key for that, I'll attach that in a minute.
(Reporter)

Comment 1

11 years ago
Created attachment 288901 [details]
public key for l10n buildbots

Updated

11 years ago
Assignee: server-ops → mrz
(Reporter)

Comment 2

11 years ago
I haven't called this out explicitly, I'll need this for both cvs.mozilla.org:/cvsroot and cvs.mozilla.org:/l10n.
(Reporter)

Comment 3

11 years ago
Beefing up the priority a bit and moving back to the pool for triage.
Assignee: mrz → server-ops
Severity: normal → major
(Assignee)

Updated

11 years ago
Assignee: server-ops → aravind
can't you just pull with -D "10 minutes ago" or something?  That would allow time for the rsync to propagate the checkins in question.
(Reporter)

Comment 5

11 years ago
Not really, because this is a buildbot, targetting at timely responses to check-ins. Delaying it artificially by 10 minutes is a significant change to the architecture that's currently running, and is a longer time than the actual build run, so having to do that would be unfortunate.
(Reporter)

Comment 6

11 years ago
If we're doing firefox 3 B2 like B1, this is an B3 l10n blocker.

Currently, localizers don't have a reasonable way to get their buildbot-based boxens green, which have more l10n test coverage than tinderbox (due to branch stability for that). Having those boxens green was a turn-on criteria for B1.
(Reporter)

Comment 7

11 years ago
(In reply to comment #6)
> If we're doing firefox 3 B2 like B1, this is an B3 l10n blocker.

Make that a Firefox 3 B2 l10n blocker.
(Assignee)

Comment 8

11 years ago
Your CVS account has been created.  Your CVSROOT should be:

   l10nbld@cvs.mozilla.org:/cvsroot

Don't forget to set your CVS_RSH environment variable to 'ssh'.

If you have any problems connecting, let me know.


Try checking out stuff with it and let me know if it doesn't work.

I will post here once I have the l10n stuff ready.
(Assignee)

Comment 9

11 years ago
Your CVS account has been created.  Your CVSROOT should be:

   l10nbld@cvs.mozilla.org:/l10n

Don't forget to set your CVS_RSH environment variable to 'ssh'.

If you have any problems connecting, let me know.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
(Reporter)

Comment 10

11 years ago
I'm having problems, sadly, ssh-ing directly into cvs.m.o works, though.

cvs -t -d l10nbld@cvs.mozilla.org:/cvsroot co mozilla/client.mk 
 -> main: Session ID is 6AO58RgJpqNQN4Is 
 -> main loop with CVSROOT=/cvsroot 
 -> safe_location( where=(null) ) 
 -> open_connection_to_server (l10nbld@cvs.mozilla.org:/cvsroot)
 -> Starting server: ssh -l l10nbld cvs.mozilla.org cvs server 
cvs server: cannot open /cvsroot/CVSROOT/config: Permission denied
Cannot access /cvsroot/CVSROOT
Permission denied
(Assignee)

Comment 11

11 years ago
Please try again and let me know if it still doesn't work.  I added you to the appropriate groups now.
(Reporter)

Comment 12

11 years ago
Works now, thanks.

Marking VERIFIED.
Status: RESOLVED → VERIFIED
(Reporter)

Comment 13

10 years ago
The ssh-key was affected by the ubuntu key badness, reopening to have the new key in this context. New key coming up, which was verified to be sane by reed.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
(Reporter)

Comment 14

10 years ago
Created attachment 320748 [details]
non-stupid public key for l10nbld
Attachment #288901 - Attachment is obsolete: true
(Assignee)

Comment 15

10 years ago
Fixed.
Status: REOPENED → RESOLVED
Last Resolved: 11 years ago10 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.