Closed Bug 692504 Opened 13 years ago Closed 13 years ago

push betas to internal mirrors automatically

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: rail)

References

Details

Attachments

(2 files, 2 obsolete files)

configs
(deleted), patch
bhearsum
: review+
rail
: checked-in+
Details | Diff | Splinter Review
buildbotcustom
(deleted), patch
rail
: review+
rail
: checked-in+
Details | Diff | Splinter Review
Betas should get pushed to internal mirrors automatically. This should be pretty easy, because there's no rsync modules to update (because we exclude *.*b* from mozilla-releases already). We probably need a flag in the release config to control this behaviour.
Assignee: nobody → rail
Priority: -- → P4
Priority: P4 → P2
We can push the files after the "updates" or antivirus builder. Probably the latter is better. Any other suggestion?
Yeah, pushing after A/V is probably best for Betas.
For betas: we need to disable "updates available on betatest" emails and add "updates available on releasetest" emails ~10 mins after pushing the files to the internal mirrors.
(In reply to Rail Aliiev [:rail] from comment #3) > For betas: we need to disable "updates available on betatest" emails and add > "updates available on releasetest" emails ~10 mins after pushing the files > to the internal mirrors. The comment about releasetest confuses me, as we already get a 'ready for releasetest testing' email when we get to weight 1 in bouncer (ie when sentry polls dm-download02). +1 to disabling the betatest emails though.
(In reply to Nick Thomas [:nthomas] from comment #4) > > The comment about releasetest confuses me, as we already get a 'ready for > releasetest testing' email when we get to weight 1 in bouncer (ie when > sentry polls dm-download02). +1 to disabling the betatest emails though. Oh, right.
Attached patch configs (deleted) — — Splinter Review
Attached patch buildbotcustom (obsolete) (deleted) — — Splinter Review
to be tested
Attached patch buildbotcustom (obsolete) (deleted) — — Splinter Review
Passed staging test
Attachment #567146 - Attachment is obsolete: true
Attachment #567924 - Flags: review?(bhearsum)
Attachment #567145 - Flags: review?(bhearsum)
Comment on attachment 567924 [details] [diff] [review] buildbotcustom Review of attachment 567924 [details] [diff] [review]: ----------------------------------------------------------------- ::: process/release.py @@ +485,5 @@ > + if releaseConfig.get('enableAutomaticPushToMirrors') and \ > + releaseConfig.get('verifyConfigs'): > + upstream_scheduler = updates_scheduler > + if not releaseConfig.get('disableVirusCheck'): > + upstream_scheduler = antivirus_scheduler Can you reverse this logic? Using "if not" on variable starting with "disable" is a bit confusing.
Attachment #567924 - Flags: review?(bhearsum) → review+
Attachment #567145 - Flags: review?(bhearsum) → review+
Attached patch buildbotcustom (deleted) — — Splinter Review
Comment on attachment 568055 [details] [diff] [review] buildbotcustom Updated patch, r=bhearsum via IRC.
Attachment #568055 - Attachment description: bui → buildbotcustom
Attachment #568055 - Flags: review+
Attachment #567924 - Attachment is obsolete: true
A reconfig that included this happened today.
Status: NEW → RESOLVED
Closed: 13 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

Creator:
Created:
Updated:
Size: