Closed Bug 623696 Opened 14 years ago Closed 11 years ago

release_sanity should work better with staging

Categories

(Release Engineering :: Release Automation, defect, P4)

Product:
Release Engineering
Component:
Release Automation
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: armenzg, Unassigned)

Details

(Whiteboard: [release][automation])

We should be able to run release_sanity.py on staging without haveing to recreate repositories a priori since we are going to re-create them with "repo_setup" as soon as the sendchanges are send. CURRENTLY: fiddle with user repos or stage-ffxbld -> release_sanity -> sendchange -> repo_setup WHAT SHOULD BE: release_sanity -> sendchange -> repo_setup [cltbld@staging-master builder_master3]$ PYTHONPATH=/builds/buildbot/builder_master3:/builds/buildbot/builder_master3/tools/lib/python python /builds/buildbot/builder_master3/tools/buildbot-helpers/release_sanity.py -u armenzg -V 4.0b9 --branch mozilla-central --build-number 1 -c staging_release-firefox-mozilla-2.0.py -b --dryrun localhost:9012 2011-01-06 12:12:52,136 : INFO : Tests Passed! Did not run reconfig/sendchange. Rerun without `-d` [cltbld@staging-master builder_master3]$ PYTHONPATH=/builds/buildbot/builder_master3:/builds/buildbot/builder_master3/tools/lib/python python /builds/buildbot/builder_master3/tools/buildbot-helpers/release_sanity.py -u armenzg -V 4.0b9 --branch mozilla-central --build-number 1 -c staging_release-firefox-mozilla-2.0.py localhost:9012 2011-01-06 12:13:20,794 : INFO : Comparing tagged revision http://hg.mozilla.org/users/armenzg_mozilla.com/buildbot-configs/raw-file/FIREFOX_4_0b9_BUILD1/mozilla/staging_release-firefox-mozilla-2.0.py to on-disk staging_release-firefox-mozilla-2.0.py ... 2011-01-06 12:13:21,059 : INFO : Comparing tagged revision http://hg.mozilla.org/users/armenzg_mozilla.com/buildbot-configs/raw-file/FIREFOX_4_0b9_BUILD1/mozilla/l10n-changesets_mozilla-2.0 to on-disk l10n-changesets_mozilla-2.0 ... 2011-01-06 12:13:21,060 : INFO : Checking for existence of http://hg.mozilla.org/mozilla-central/rev/84d3ca5ad17a... 2011-01-06 12:13:21,068 : INFO : Got: http://hg.mozilla.org/mozilla-central/rev/84d3ca5ad17a ! 2011-01-06 12:13:21,077 : ERROR : cannot find http://hg.mozilla.org/users/stage-ffxbld/mozilla-central/raw-file/84d3ca5ad17a/browser/config/version.txt. Check again, or -b to bypass 2011-01-06 12:13:21,077 : CRITICAL : Tests Failed! Not running sendchange!
I hit this problem again today. bhearsum pointed me out to this code and it says it should have worked: http://hg.mozilla.org/build/tools/rev/aff57c1ffe42
Assignee: nobody → bhearsum
Priority: -- → P3
Whiteboard: [releases][release sanity] → [release][automation]
Assignee: bhearsum → nobody
Priority: P3 → P4
Product: mozilla.org → Release Engineering
Component: Other → Release Automation
QA Contact: bhearsum
This workflow is a lot better now that we have Ship It/release runner. I don't think this is worth fixing now. https://wiki.mozilla.org/Release:Release_Automation_on_Mercurial:Staging_Specific_Notes#How_to_start_a_staging_release
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.