411495 - sync up automation buildbot/bootstrap configs with cvs

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P2)

Description

[[e-mail] (:bhearsum)]

Attachment: updated buildbot configs, sans passwords

Once again these configs have fallen out of sync with cvs. Here's a couple of patches to update them.

By the way, Rob. When I went to update the tinder-config's on the cvs mirror I'd found that they'd already been updated. It turns out that the nightly bootstrap.cfg had an outdated pullDate, d'oh ;). That burns me far too often.

Comment 1

[[e-mail] (:bhearsum)]

Attachment: [checked in] diff the right directory this time

Comment 2

[[e-mail] (:bhearsum)]

Attachment: [checked in] update pull times for nightly and release bootstraps

Comment 3

[[e-mail] (:bhearsum)]

Attachment: [checked in] updated production-1.9 config

Comment 4

[Robert Helmer [:rhelmer]]

Comment on attachment 296183 [details] [diff] [review]
[checked in] updated production-1.9 config

>Index: master.cfg
>===================================================================
>RCS file: /cvsroot/mozilla/tools/buildbot-configs/automation/production-1.9/master.cfg,v
>retrieving revision 1.1
>diff -u -r1.1 master.cfg
>--- master.cfg	11 Dec 2007 01:35:58 -0000	1.1
>+++ master.cfg	9 Jan 2008 19:23:29 -0000
>@@ -104,6 +103,27 @@
>                    command=['make', 'clean_logs'], haltOnFailure=1)
> tagFactory.addStep(ShellCommand, description='unit tests',
>                    command=['make', 'test'], haltOnFailure=1)
>+# The Makefile 'stage' targets are Fx2 specific, we have to do our own thing
>+# here. Previous builds/updates need to be downloaded manually, at this time.

This is a good point, maybe what we should do on both staging machines is to have "prestage" factory that run at the beginning, and not use the Makefile for this anymore.

This probably shouldn't be part of Tag as it makes it confusing what belongs in production tagFactory and what doesn't.

Comment 5

[[e-mail] (:bhearsum)]

Comment on attachment 296142 [details] [diff] [review]
[checked in] update pull times for nightly and release bootstraps

Checking in fx-moz19-nightly-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz19-nightly-bootstrap.cfg,v  <--  fx-moz19-nightly-bootstrap.cfg
new revision: 1.2; previous revision: 1.1
done
Checking in fx-moz19-staging-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz19-staging-bootstrap.cfg,v  <--  fx-moz19-staging-bootstrap.cfg
new revision: 1.6; previous revision: 1.5
done

Comment 6

[[e-mail] (:bhearsum)]

Comment on attachment 296183 [details] [diff] [review]
[checked in] updated production-1.9 config

Checking in master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/automation/production-1.9/master.cfg,v  <--  master.cfg
new revision: 1.2; previous revision: 1.1
done

Comment 7

[[e-mail] (:bhearsum)]

(In reply to comment #4)
> (From update of attachment 296183 [details] [diff] [review])
> >Index: master.cfg
> >===================================================================
> >RCS file: /cvsroot/mozilla/tools/buildbot-configs/automation/production-1.9/master.cfg,v
> >retrieving revision 1.1
> >diff -u -r1.1 master.cfg
> >--- master.cfg	11 Dec 2007 01:35:58 -0000	1.1
> >+++ master.cfg	9 Jan 2008 19:23:29 -0000
> >@@ -104,6 +103,27 @@
> >                    command=['make', 'clean_logs'], haltOnFailure=1)
> > tagFactory.addStep(ShellCommand, description='unit tests',
> >                    command=['make', 'test'], haltOnFailure=1)
> >+# The Makefile 'stage' targets are Fx2 specific, we have to do our own thing
> >+# here. Previous builds/updates need to be downloaded manually, at this time.
> 
> This is a good point, maybe what we should do on both staging machines is to
> have "prestage" factory that run at the beginning, and not use the Makefile for
> this anymore.
> 
> This probably shouldn't be part of Tag as it makes it confusing what belongs in
> production tagFactory and what doesn't.
> 

I filed bug 411546 as a follow-up for this.

Comment 8

[[e-mail] (:bhearsum)]

Attachment: [checked in] use the right cvsroot

Comment 9

[[e-mail] (:bhearsum)]

Comment on attachment 296199 [details] [diff] [review]
[checked in] use the right cvsroot

Checking in production-1.9/master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/automation/production-1.9/master.cfg,v  <--  master.cfg
new revision: 1.3; previous revision: 1.2
done

Comment 10

[[e-mail] (:bhearsum)]

Comment on attachment 296140 [details] [diff] [review]
[checked in] diff the right directory this time

Checking in staging-1.9/master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/automation/staging-1.9/master.cfg,v  <--  master.cfg
new revision: 1.5; previous revision: 1.4
done

Comment 11

[[e-mail] (:bhearsum)]

Attachment: [checked in] add nightly 1.8 bootstrap.cfg, update staging 1.8

The production bootstrap.cfg is out of date on build-console. However, the Buildbot config pulls from an old tag, so it's appropriate. I'm not sure if this is wanted/expected, but I didn't want to update either without checking.

Comment 12

[[e-mail] (:bhearsum)]

Attachment: [checked in] update cvs with current master.cfg on staging-b-c

Comment 13

[Robert Helmer [:rhelmer]]

Comment on attachment 296227 [details] [diff] [review]
[checked in] add nightly 1.8 bootstrap.cfg, update staging 1.8

Hmm I think it should be ok to update the pullDate, I've had to push it up before to pull in local changes but I don't think there's any reason for it to be out of date.

Comment 14

[[e-mail] (:bhearsum)]

Attachment: [checked in] bump cleanup job on 1.9 automation to cleanup 2008* directories

(This bug is getting out of hand, heh.)

Comment 15

[[e-mail] (:bhearsum)]

Comment on attachment 296229 [details] [diff] [review]
[checked in] update cvs with current master.cfg on staging-b-c

Checking in staging/master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/automation/staging/master.cfg,v  <--  master.cfg
new revision: 1.12; previous revision: 1.11
done

Comment 16

[Robert Helmer [:rhelmer]]

Comment on attachment 296326 [details] [diff] [review]
[checked in] bump cleanup job on 1.9 automation to cleanup 2008* directories

Hmm.. why don't we remove "/home/ftp/pub/firefox/nightly/*"?

Comment 17

[[e-mail] (:bhearsum)]

(In reply to comment #16)
> (From update of attachment 296326 [details] [diff] [review])
> Hmm.. why don't we remove "/home/ftp/pub/firefox/nightly/*"?
> 

At this time, staging trunk automation doesn't pull down the old builds on every run, so if we did that it would clobber this. :). This is something else that we could/should fix in the prestage factory.

Comment 18

[[e-mail] (:bhearsum)]

Comment on attachment 296227 [details] [diff] [review]
[checked in] add nightly 1.8 bootstrap.cfg, update staging 1.8

Checking in fx-moz18-nightly-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz18-nightly-bootstrap.cfg,v  <--  fx-moz18-nightly-bootstrap.cfg
initial revision: 1.1
done
Checking in fx-moz18-staging-bootstrap.cfg;
/cvsroot/mozilla/tools/release/configs/fx-moz18-staging-bootstrap.cfg,v  <--  fx-moz18-staging-bootstrap.cfg
new revision: 1.11; previous revision: 1.10
done

Comment 19

[[e-mail] (:bhearsum)]

Comment on attachment 296326 [details] [diff] [review]
[checked in] bump cleanup job on 1.9 automation to cleanup 2008* directories

Checking in staging-1.9/master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/automation/staging-1.9/master.cfg,v  <--  master.cfg
new revision: 1.6; previous revision: 1.5
done