Closed Bug 1313434 Opened 8 years ago Closed 8 years ago

tracking bug for build and release of Firefox 47.0.2

Categories

(Release Engineering :: Release Requests, defect)

Product:
Release Engineering
Component:
Release Requests
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

Attachments

(1 file)

Bug 1313434 - tracking bug for build and release of Firefox 47.0.2
58 bytes, text/x-review-board-request
catlee
: review+
rail
: checked-in+
Details 
This release is special. Need to follow instructions from https://bugzilla.mozilla.org/show_bug.cgi?id=1309894#c34
tools:

$ hg up FIREFOX_47_0_1_RELEASE_RUNTIME
$ hg branch FIREFOX_47_0_2
$ hg commit -m "Bug 1313434: create FIREFOX_47_0_2 branch"
$ hg push --new-branch
pushing to ssh://hg.mozilla.org/build/tools
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 0 changes to 0 files (+1 heads)
remote: recorded push in pushlog
remote:
remote: View your change here:
remote:   https://hg.mozilla.org/build/tools/rev/54d6a274de4eee36bbc381b07bdd9c0de6512bf9
Comment on attachment 8805217 [details]
Bug 1313434 - tracking bug for build and release of Firefox 47.0.2

https://reviewboard.mozilla.org/r/88998/#review88152

/me crosses fingers
Attachment #8805217 - Flags: review?(catlee) → review+
Comment on attachment 8805217 [details]
Bug 1313434 - tracking bug for build and release of Firefox 47.0.2

https://hg.mozilla.org/build/buildbot-configs/rev/bcb07cf862bf0221139589661b5625ad99f9b9b3
Attachment #8805217 - Flags: checked-in+
In mozilla-unified repo:

$ hg up FIREFOX_47_0_1_RELEASE
$ hg branch FIREFOX_47_0_2_RELBRANCH
$ hg commit -m "Create FIREFOX_47_0_2_RELBRANCH"
$ hg graft e879961960ee
grafting 323397:e879961960ee "Bug 848284, support for running l10n on try, r=catlee DONTBUILD"
merging testing/mozharness/configs/single_locale/macosx64.py
$ hg graft 5e0c246f9a60        
grafting 330882:5e0c246f9a60 "Bug 1277640 - desktop_l10n.py should clone gecko by revision r=Callek a=release DONTBUILD"
merging testing/mozharness/configs/single_locale/mozilla-beta.py
merging testing/mozharness/configs/single_locale/mozilla-esr45.py
merging testing/mozharness/configs/single_locale/mozilla-release.py
$ vi testing/mozharness/configs/releases/updates_firefox_release.py # adjust tools repo revision, set to FIREFOX_47_0_2
$ vi testing/mozharness/configs/releases/postrelease_firefox_release.py  # adjust mozilla-release revision, set to FIREFOX_47_0_2_RELBRANCH
$ vi browser/config/version* config/milestone.txt  # bump version 47.0.1 -> 47.0.2
$ hg commit -m " Bug 1313434: Use FIREFOX_47_0_2_RELBRANCH fro 47.0.2 release r=me a=release"
$ hg out -r . release
comparing with release
searching for changes
changeset:   366324:a39c838b0cdd
branch:      FIREFOX_47_0_2_RELBRANCH
parent:      332463:7f5abf95991b
user:        Rail Aliiev <rail@mozilla.com>
date:        Thu Oct 27 14:20:41 2016 -0400
summary:     Create FIREFOX_47_0_2_RELBRANCH

changeset:   366325:b15b6e49e835
branch:      FIREFOX_47_0_2_RELBRANCH
user:        Nick Thomas <nthomas@mozilla.com>
date:        Thu Apr 28 10:53:07 2016 +1200
summary:     Bug 848284, support for running l10n on try, r=catlee DONTBUILD

changeset:   366326:518b33719cd5
branch:      FIREFOX_47_0_2_RELBRANCH
user:        Rail Aliiev <rail@mozilla.com>
date:        Thu Jun 02 15:30:16 2016 -0400
summary:     Bug 1277640 - desktop_l10n.py should clone gecko by revision r=Callek a=release DONTBUILD

changeset:   366327:8b3f870ddb0f
branch:      FIREFOX_47_0_2_RELBRANCH
tag:         tip
user:        Rail Aliiev <rail@mozilla.com>
date:        Thu Oct 27 14:24:48 2016 -0400
summary:     Bug 1313434: Use FIREFOX_47_0_2_RELBRANCH fro 47.0.2 release r=me a=release

$ hg push -r . --new-branch release
pushing to ssh://hg.mozilla.org/releases/mozilla-release
searching for changes
remote: adding changesets                                                                                                                                                                                                                                                        
remote: adding manifests
remote: adding file changes
remote: added 4 changesets with 7 changes to 7 files (+1 heads)
remote: recorded push in pushlog
remote:
remote: View your changes here:
remote:   https://hg.mozilla.org/releases/mozilla-release/rev/a39c838b0cdd98bf37af565fc15d745f95b8a57e
remote:   https://hg.mozilla.org/releases/mozilla-release/rev/b15b6e49e83565804752af242c74473ef8a04793
remote:   https://hg.mozilla.org/releases/mozilla-release/rev/518b33719cd51ca3baeb29e7f02e96bf3dc69dc7
remote:   https://hg.mozilla.org/releases/mozilla-release/rev/8b3f870ddb0f38f877d169f7832c2d136e4f2943
remote:
remote: Follow the progress of your build on Treeherder:
remote:   https://treeherder.mozilla.org/#/jobs?repo=mozilla-release&revision=8b3f870ddb0f38f877d169f7832c2d136e4f2943
remote: recorded changegroup in replication log in 0.008s
FTR, we shouldn't run the update aliases as a part of postrelease because we don't want to change the "latest" entries in bouncer.

I can think of 2 ways to avoid this:

* run it and revert it (manually)
* do not resolve the human decision task, schedule the tasks individually
In Balrog I did the following:

* reverted the release-localtest default rule (56) to 49.0.2-build2
* cloned rule  413 (release*) to release-localtest, bumped the priority from 110 to 111, set the blob to 47.0.2-build1 (from 47.0.1)
* reverted the release-cdntest default rule (57) to 49.0.2-build2
* cloned rule  413 (release*) to release-cdtest, bumped the priority from 110 to 111, set the blob to 47.0.2-build1 (from 47.0.1)
(In reply to Rail Aliiev [:rail] from comment #7)
> FTR, we shouldn't run the update aliases as a part of postrelease because we
> don't want to change the "latest" entries in bouncer.
> 
> I can think of 2 ways to avoid this:
> 
> * run it and revert it (manually)
> * do not resolve the human decision task, schedule the tasks individually

The same applies to the publish to balrog job

Probably it'd be better just to force schedule the version bump and mark as shipped jobs.
Depends on: 1314131
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: