Closed Bug 401290 Opened 17 years ago Closed 17 years ago

Update verify config needs to use externalAusServer

Categories

(Release Engineering :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: nthomas)

References

Details

Attachments

(1 file)

We currently use the bootstrap.cfg setting ausServer to set both the server to upload updates to (via ssh), and the server to test updates (via http). This works fine for staging, but production uses separate servers for these. The simplest fix I can think of is to make an externalAusServer setting in bootstrap.cfg, and use that for testing.
We should add "externalAusServer" to both fx-moz18-bootstrap.cfg and fx-moz18-staging-bootstrap.cfg. For staging, the value for ausServer and externalAusServer would be the same for now, but it feels more consistent with how we would be doing production... $0.02.
Assignee: nobody → nrthomas
Priority: P3 → P2
This patch makes the suggested changes in comments 0 and 1. It also hardcodes the https protocol - I found with Tb2009rc1 that we weren't specifying a protocol, so wget defaulted to http, and only some of machines behind aus2.m.o correctly redirected to https, leading to spurious FAIL results.
Attachment #287106 - Flags: review?(rhelmer)
Attachment #287106 - Flags: review?(joduinn)
Attachment #287106 - Flags: review?(joduinn) → review+
Comment on attachment 287106 [details] [diff] [review] Add externalAusServer and use it in Updates::BumpVerifyConfig looks good, we should make sure this gets in the shipping configs (might as well add it now)
Attachment #287106 - Flags: review?(rhelmer) → review+
Checking in Bootstrap/Step/Updates.pm; /cvsroot/mozilla/tools/release/Bootstrap/Step/Updates.pm,v <-- Updates.pm new revision: 1.26; previous revision: 1.25 done Checking in configs/fx-moz18-bootstrap.cfg; /cvsroot/mozilla/tools/release/configs/fx-moz18-bootstrap.cfg,v <-- fx-moz18-bootstrap.cfg new revision: 1.22; previous revision: 1.21 done Checking in configs/fx-moz18-staging-bootstrap.cfg; /cvsroot/mozilla/tools/release/configs/fx-moz18-staging-bootstrap.cfg,v <-- fx-moz18-staging-bootstrap.cfg new revision: 1.7; previous revision: 1.6 done Checking in configs/fx-moz180-bootstrap.cfg; /cvsroot/mozilla/tools/release/configs/fx-moz180-bootstrap.cfg,v <-- fx-moz180-bootstrap.cfg new revision: 1.5; previous revision: 1.4 done Checking in configs/tb-moz18-bootstrap.cfg; /cvsroot/mozilla/tools/release/configs/tb-moz18-bootstrap.cfg,v <-- tb-moz18-bootstrap.cfg new revision: 1.11; previous revision: 1.10 done Checking in configs/tb-moz180-bootstrap.cfg; /cvsroot/mozilla/tools/release/configs/tb-moz180-bootstrap.cfg,v <-- tb-moz180-bootstrap.cfg new revision: 1.6; previous revision: 1.5 done
Status: NEW → RESOLVED
Closed: 17 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.

Attachment

General

Created:
Updated:
Size: