Releases/Firefox 34.0/BuildNotes: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(build2 are go)
(→‎Running tests: bummer, can't twist the automation;s arm)
Line 47: Line 47:


==== Running tests ====
==== Running tests ====
Rather than grabbing 3 slaves and running these manually, we may be able to twist the automation's arm:
Rather than grabbing 3 slaves and running these manually, we ''may'' be able to twist the automation's arm:
* wait until we get the 'updates available on betatest' email
* wait until we get the 'updates available on betatest' email
* commit the config patch to tools  (no fallout from this on next release)
* commit the config patch to tools  (no fallout from this on next release)
* force the beta update verify jobs (eg release-mozilla-beta-linux_update_verify_1/6). We'd need to set the '''script_repo_revision''' property to the revision when that landed
* force the beta update verify jobs (eg release-mozilla-beta-linux_update_verify_1/6). We'd need to set the '''script_repo_revision''' property to the revision when that landed


The emails we get back will be labelled 34.0b11, but I don't think it's worth bumping the release config and reconfiging just to avoid that.
The emails we get back would be labelled 34.0b11, but I don't think it's worth bumping the release config and reconfiging just to avoid that.
 
--> Turns out this doesn't work, script_repo_revision was still set to FIREFOX_34_0b11_RELEASE_RUNTIME.


= Firefox 34.0 build2 =
= Firefox 34.0 build2 =

Revision as of 03:37, 26 November 2014

bug 1104416

Firefox 34.0 build1

Checklist

Issues

  • a single locale, ta, has failed in chunk 9/10 win32, restarted standalone repack (bad slave/disk space issue?), triggered release-mozilla-release-win32_repack_complete manually

Updates for beta

cf 33.0 notes

  • partial from 34.0b11 generated at build time (from this patch)
  • release blob looks goo
  • added bouncer product/locations for beta-cdntest/beta:
Product				OS	Path
Firefox-34.0-Partial-34.0b11	win	/firefox/candidates/34.0-candidates/build1/update/win32/:lang/firefox-34.0b11-34.0.partial.mar
Firefox-34.0-Partial-34.0b11	osx	/firefox/candidates/34.0-candidates/build1/update/mac/:lang/firefox-34.0b11-34.0.partial.mar
Firefox-34.0-Partial-34.0b11	linux64	/firefox/candidates/34.0-candidates/build1/update/linux-x86_64/:lang/firefox-34.0b11-34.0.partial.mar
Firefox-34.0-Partial-34.0b11	linux	/firefox/candidates/34.0-candidates/build1/update/linux-i686/:lang/firefox-34.0b11-34.0.partial.mar

Update verify

Prep

On nthomas' laptop, after en-US builds done:

cd <parent_of_tools_checkout, updated to tip>
export PERL5LIB="tools/lib/perl:$HOME/perl5/lib/perl5"  # need Config::General v2.44
wget http://hg.mozilla.org/releases/mozilla-release/raw-file/FIREFOX_34_0_RELEASE/browser/locales/shipped-locales
perl tools/release/patcher-config-bump.pl -p firefox -r Firefox -v 34.0 -a 34.0 -o 34.0b11 -b 1 \
  -c tools/release/patcher-configs/mozBeta-branch-patcher2.cfg -t stage.mozilla.org -f ftp.mozilla.org \
  -d download.mozilla.org -l shipped-locales --partial-version 34.0b11 --platform linux --platform linux64 \
  --platform macosx64 --platform win32

# generate update verify configs
python tools/scripts/updates/create-update-verify-configs.py -c tools/release/patcher-configs/mozBeta-branch-patcher2.cfg --platform linux64 --output tools/release/updates/mozBeta-firefox-linux64.cfg --release-config-file mozilla/release-firefox-mozilla-release.py -b https://hg.mozilla.org/build/buildbot-configs --channel beta-cdntest -t FIREFOX_34_0_RELEASE
python tools/scripts/updates/create-update-verify-configs.py -c tools/release/patcher-configs/mozBeta-branch-patcher2.cfg --platform linux --output tools/release/updates/mozBeta-firefox-linux.cfg --release-config-file mozilla/release-firefox-mozilla-release.py -b https://hg.mozilla.org/build/buildbot-configs --channel beta-cdntest -t FIREFOX_34_0_RELEASE
python tools/scripts/updates/create-update-verify-configs.py -c tools/release/patcher-configs/mozBeta-branch-patcher2.cfg --platform macosx64 --output tools/release/updates/mozBeta-firefox-mac64.cfg --release-config-file mozilla/release-firefox-mozilla-release.py -b https://hg.mozilla.org/build/buildbot-configs --channel beta-cdntest -t FIREFOX_34_0_RELEASE
python tools/scripts/updates/create-update-verify-configs.py -c tools/release/patcher-configs/mozBeta-branch-patcher2.cfg --platform win32 --output tools/release/updates/mozBeta-firefox-win32.cfg --release-config-file mozilla/release-firefox-mozilla-release.py -b https://hg.mozilla.org/build/buildbot-configs --channel beta-cdntest -t FIREFOX_34_0_RELEASE

hg -R tools/ diff tools/release/updates > patch

Attached to bug 1071606 as attachment 8528267.

Running tests

Rather than grabbing 3 slaves and running these manually, we may be able to twist the automation's arm:

  • wait until we get the 'updates available on betatest' email
  • commit the config patch to tools (no fallout from this on next release)
  • force the beta update verify jobs (eg release-mozilla-beta-linux_update_verify_1/6). We'd need to set the script_repo_revision property to the revision when that landed

The emails we get back would be labelled 34.0b11, but I don't think it's worth bumping the release config and reconfiging just to avoid that.

--> Turns out this doesn't work, script_repo_revision was still set to FIREFOX_34_0b11_RELEASE_RUNTIME.

Firefox 34.0 build2

Checklist

Issues

  • don't need to modify extraPartials, as we didn't ship build1 to beta channel

Updates for beta

Fennec 34.0 build1

Checklist

Issues

  • android repacks all failed in configure with java < 1.7, we missed bug 1082325. Patch landed, updated tags and re-triggered jobs, all green.
  • email '[release] Fennec 34.0 build1: Updates available on None' with content 'Updates to Fennec 34.0 build1 are now ready for testing on the None channel.' Commented on bug 1019724.

Fennec 34.0 build2

Checklist

Issues

Retrieved from "https://wiki.mozilla.org/index.php?title=Releases/Firefox_34.0/BuildNotes&oldid=1036886"