Closed Bug 389206 Opened 12 years ago Closed 12 years ago

set up staging AUS server on staging-build-console

Categories

(Release Engineering :: General, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: rhelmer)

References

Details

(Whiteboard: waiting for 373995)

Attachments

(3 files, 1 obsolete file)

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.
Assignee: build → rhelmer
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: ETA: july 27
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

Priority: P2 → P3
Whiteboard: ETA: july 27
Depends on: 373995
Whiteboard: waiting for 373995
Assignee: rhelmer → build
Status: ASSIGNED → NEW
(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.

Status: NEW → ASSIGNED
Assignee: build → rhelmer
Status: ASSIGNED → NEW
Attached patch push -test snippets live (obsolete) — Splinter Review
Attachment #284649 - Flags: review?(nrthomas)
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.
Attachment #284649 - Flags: review?(nrthomas) → review-
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.
Attachment #284649 - Attachment is obsolete: true
Attachment #284653 - Flags: review?(nrthomas)
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.
Attachment #284653 - Flags: review?(nrthomas) → review+
Attachment #284661 - Flags: review?(nrthomas) → review+
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
Attachment #284661 - Attachment description: ausServer should be staging-b-c not localhost → [checked in] ausServer should be staging-b-c not localhost
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
Attachment #284653 - Attachment description: use aus key and ausUser → [checked in]use aus key and ausUser
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.
Attachment #284714 - Flags: review?(nrthomas)
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 ?
Attachment #284714 - Flags: review?(nrthomas) → review+
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
Attachment #284714 - Attachment description: hook up push and announce in buildbot master.cfg → [checked in]hook up push and announce in buildbot master.cfg
(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.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.