389206 - set up staging AUS server on staging-build-console

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Robert Helmer [:rhelmer]]

In order to do a complete end-to-end run, we must have a simple AUS server set up in the testing environment, for the Update->Push and Update->Verify. 

This is fine to go on staging-build-console, for now.

Comment 1

[Robert Helmer [:rhelmer]]

AUS is installed and the the file path is set up so Update->Push works, but this is kind of a moot point until:

1) Update->Push is able to push snippets live (only goes to staging area for now)
2) updateVerify is totally auto-configured

Comment 2

[Robert Helmer [:rhelmer]]

(In reply to comment #1)
> AUS is installed and the the file path is set up so Update->Push works, but
> this is kind of a moot point until:
> 
> 1) Update->Push is able to push snippets live (only goes to staging area for
> now)
> 2) updateVerify is totally auto-configured

#2 works, I'm going to work on #1 now and finish the staging AUS server setup on staging-build-console.

Comment 3

[Robert Helmer [:rhelmer]]

Attachment: push -test snippets live

Comment 4

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

Comment on attachment 284649 [details] [diff] [review]
push -test snippets live 

>+    # Push test channels live
>+    $this->Shell(
>+      cmd => 'ssh',
>+      cmdArgs => [$ausServer, '/home/cltbld/bin/pushsnip', $pushDir . '-test'],
>+      logFile => $pushLog,
>+    );
> }

You can't skip specifying the aus key, or for consistency shouldn't skip using $ausUser. See the Shell call immediately above this block.

Comment 5

[Robert Helmer [:rhelmer]]

Attachment: [checked in]use aus key and ausUser

Right, thanks :)

Also I modified the announcement message as per our irc discussion.. current assumption is that it'll be called after Execute/Push but before Verify.

Comment 6

[Robert Helmer [:rhelmer]]

Attachment: [checked in] ausServer should be staging-b-c not localhost

Comment 7

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

Comment on attachment 284653 [details] [diff] [review]
[checked in]use aus key and ausUser

r+, looks good. Would be nice to take another look at our tests before using this in a production setting.

Comment 8

[Robert Helmer [:rhelmer]]

Comment on attachment 284661 [details] [diff] [review]
[checked in] ausServer should be staging-b-c not localhost

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.6; previous revision: 1.5
done

Comment 9

[Robert Helmer [:rhelmer]]

Comment on attachment 284653 [details] [diff] [review]
[checked in]use aus key and ausUser

Checking in Bootstrap/Step/Updates.pm;
/cvsroot/mozilla/tools/release/Bootstrap/Step/Updates.pm,v  <--  Updates.pm
new revision: 1.20; previous revision: 1.19
done

Comment 10

[Robert Helmer [:rhelmer]]

Attachment: [checked in]hook up push and announce in buildbot master.cfg

This all works fine on staging, but it needs to be hooked up before it'll show in the end-to-end run :)

Also note that I remove $ausDeliveryDir from Updates->Announce() because bootstrap is being run like "./release -o Updates -a" so it won't have access to that variable.

Comment 11

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

Comment on attachment 284714 [details] [diff] [review]
[checked in]hook up push and announce in buildbot master.cfg

Looks good. What's the plan for keeping production in sync with staging ? Update after 2.0.0.8 goes out ?

Comment 12

[Robert Helmer [:rhelmer]]

Comment on attachment 284714 [details] [diff] [review]
[checked in]hook up push and announce in buildbot master.cfg

Checking in release/Bootstrap/Step/Updates.pm;
/cvsroot/mozilla/tools/release/Bootstrap/Step/Updates.pm,v  <--  Updates.pm
new revision: 1.23; previous revision: 1.22
done
Checking in buildbot-configs/automation/staging/master.cfg;
/cvsroot/mozilla/tools/buildbot-configs/automation/staging/master.cfg,v  <--  master.cfg
new revision: 1.7; previous revision: 1.6
done

Comment 13

[Robert Helmer [:rhelmer]]

(In reply to comment #11)
> (From update of attachment 284714 [details] [diff] [review])
> Looks good. What's the plan for keeping production in sync with staging ?
> Update after 2.0.0.8 goes out ?

I think we should add a check to compare the staging/production configs to http://wiki.mozilla.org/Build:Release_Automation#Current_status (or whatever pre-release checklist we want to use).

We need to do the same thing to compare the bootstrap changes and see if they're ready for the next release and tag if so.