Closed Bug 798361 Opened 12 years ago Closed 12 years ago

Make release automation work with mock slaves [when 18 merges to beta]

Categories

(Release Engineering :: Release Automation, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jhopkins, Assigned: jhopkins)

References

Details

Attachments

(3 files, 7 obsolete files)

No description provided.
Depends on: 803080
Depends on: 803166
Comment on attachment 673232 [details] [diff] [review] look for python in the PATH before using hard coded value Review of attachment 673232 [details] [diff] [review]: ----------------------------------------------------------------- ::: scripts/release/tagging.sh @@ +5,5 @@ > SCRIPTS_DIR="$MY_DIR/../../" > +PYTHON=`which python` > +if [ -z "$PYTHON" ]; then > + PYTHON=/tools/python/bin/python > +fi This would point to default python2.4 on the old machines. You need to test if /tools/python/bin/python exists, then use system python. Something like: PYTHON=$(test -x /tools/python/bin/python || which python)
Attachment #673232 - Flags: review?(rail) → review-
Attached patch buildbot-configs patch (obsolete) — Splinter Review
Attachment #673285 - Flags: review?(rail)
Attachment #673287 - Flags: feedback?(rail)
Addressed feedback and kept '-x' addition because I think there's enough going on here that it would be useful log output to have.
Attachment #673288 - Flags: review?(rail)
Attached patch buildbotcustom patch (obsolete) — Splinter Review
(note: obsoleting old tools patch at the same time)
Attachment #673232 - Attachment is obsolete: true
Attachment #673295 - Flags: review?(rail)
Attached patch mozharness patch (obsolete) — Splinter Review
Attachment #673299 - Flags: review?(rail)
Attachment #673288 - Flags: review?(rail) → review+
Comment on attachment 673285 [details] [diff] [review] buildbot-configs patch Review of attachment 673285 [details] [diff] [review]: ----------------------------------------------------------------- I was unable to pass even the first step of the release process (tagging). It was failing with the following: remote: Warning: Identity file ~cltbld/.ssh/ffxbld_dsa not accessible: No such file or directory. remote: Permission denied (publickey,keyboard-interactive). abort: no suitable response from remote hg! It comes from releaseConfig['hgSshKey']. cltbld doesn't exist under mock. Changing ~cltbld/.ssh/ to ~/.ssh/ may work. However, I don't understand why you need to change HOME environment variable... Looks like setting it doesn't work at all. I believe that HOME is special. ::: mozilla/config.py @@ +131,5 @@ > 'enable_shared_checkouts': True, > 'env': { > 'DISPLAY': ':2', > 'HG_SHARE_BASE_DIR': '/builds/hg-shared', > + 'HOME': '/home/mock_mozilla', This one doesn't work as expected: $ mock_mozilla -r mozilla-centos6-i386 --cwd /builds/slave/rel-m-beta-firefox-tag/. --unpriv --shell '/usr/bin/env HOME="/home/mock_mozilla" echo "HOME: $HOME"' INFO: mock_mozilla.py version 1.0.3 starting... State Changed: init plugins INFO: selinux disabled State Changed: start State Changed: lock buildroot State Changed: shell HOME: /builds State Changed: unlock buildroot Additionally it may change a lot of other things. At least it may break old style releases. @@ +175,5 @@ > 'mock_copyin_files': [ > ('/home/cltbld/.ssh', '/home/mock_mozilla/.ssh'), > + ('/home/cltbld/.android', '/home/mock_mozilla/.android'), > + ('/home/cltbld/.mozpass.cfg', '/home/mock_mozilla/.mozpass.cfg'), > + ('/home/cltbld/.hgrc', '/home/mock_mozilla/.hgrc'), These changes break hg share extension, what means that at least .hgrc goes under a wrong directory. (hg: unknown command 'share' in the logs)
Attachment #673285 - Flags: review?(rail) → review-
Comment on attachment 673287 [details] [diff] [review] thunderbird buildbot-configs changes (wip, needs testing) See my comments for config.py
Attachment #673287 - Flags: feedback?(rail) → feedback-
Comment on attachment 673295 [details] [diff] [review] buildbotcustom patch Review of attachment 673295 [details] [diff] [review]: ----------------------------------------------------------------- in overall it looks good, except this blocker: ::: process/release.py @@ +965,5 @@ > partner_repack_factory = ScriptFactory( > scriptRepo=mozharness_repo, > scriptName=mh_cfg['script'], > extra_args=extra_args, > + use_mock=use_mock(platform), Partner repack factory shouldn't use mock, because we can run it only on mack slaves. It didn't pass checkconfig when I enabled partner repacks in the configs. Either remove mock_* parameter, or explicitly set use_mock to False here.
Attachment #673295 - Flags: review?(rail) → review-
Comment on attachment 673299 [details] [diff] [review] mozharness patch the same issue as with config.py...
Attachment #673299 - Flags: review?(rail) → review-
Blocks: 805587
Attached patch [buildbot-configs] updated patch (obsolete) — Splinter Review
Attachment #673285 - Attachment is obsolete: true
Attachment #673299 - Attachment is obsolete: true
Attached patch [buildbotcustom] updated patch (obsolete) — Splinter Review
Attachment #673295 - Attachment is obsolete: true
Depends on: 806499
Attachment #675675 - Attachment is obsolete: true
Attachment #677825 - Flags: feedback?(rail)
Attachment #677825 - Flags: feedback?(catlee)
Comment on attachment 677825 [details] [diff] [review] [buildbotcustom] updated patch lgtm
Attachment #677825 - Flags: feedback?(rail) → feedback+
Comment on attachment 677825 [details] [diff] [review] [buildbotcustom] updated patch Review of attachment 677825 [details] [diff] [review]: ----------------------------------------------------------------- lgtm too. what diffs does this generate with the existing release configs?
Attachment #677825 - Flags: feedback?(catlee) → feedback+
Attachment #677825 - Flags: review+
Attachment #677825 - Flags: checked-in+
In production
Blocks: 786550
Attachment #675674 - Attachment is obsolete: true
Attachment #680643 - Flags: review?(rail)
Comment on attachment 680643 [details] [diff] [review] [buildbot-configs] updated patch lgtm!
Attachment #680643 - Flags: review?(rail) → review+
Attachment #673287 - Attachment is obsolete: true
Summary: Make release automation work with mock slaves → Make release automation work with mock slaves [when 18 merges to beta]
Attachment #680643 - Flags: checked-in+
Comment on attachment 680643 [details] [diff] [review] [buildbot-configs] updated patch in production
Status: NEW → RESOLVED
Closed: 12 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: