Closed Bug 1110286 Opened 5 years ago Closed 5 years ago

Pin mozharness in all trees

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set

Tracking

(firefox38 fixed, b2g-v2.1S fixed)

RESOLVED FIXED
Tracking Status
firefox38 --- fixed
b2g-v2.1S --- fixed

People

(Reporter: armenzg, Assigned: armenzg)

References

Details

Attachments

(9 files)

Bug 791924 is proving to be very valuable for many people.

Enabling pinning of mozharness in all trees will enable us to not worry anymore about backward compatibility, ride the trains and allows to be backed out.

Once we enable this everywhere we won't need to merge changes from default to production but land a mozharness.json change to start testing the new code.

For release jobs that do not script_repo_manifest the need to merge from default to production will still be in place.
Depends on: 1113144
As a summary we need to enable this on one integration tree and see how we handle the extra load and no issues happen.

After that, all trunk trees and wait.

If no issues, all remaining release trees.
Depends on: 1118267
No longer depends on: 1113144
No longer depends on: 1118267
There are no more blockers before proceeding with this.
Assignee: nobody → armenzg
Eventually we will also enable it on m-c and after that all trunk trees and then all release trees.

I want to increase the usage of repository_manifest.py and make sure that no new edge cases are discovered.

I also want to make sure that branches that have different set of jobs like nightly or repacks don't hit weird code paths.

We should be fine but it's better to be cautious.
Attachment #8551374 - Flags: review?(rail)
Attachment #8551374 - Flags: review?(rail) → review+
I needed to backout the pinning on fx-team due to some issues with talos pgo.

I will be adding pgo, nightly and l10n repacks for Ash before we try again.

Pinning for esr31 is not ready.
Attachment #8551374 - Flags: checked-in-
Builders added:
+ Android armv7 API 11+ ash debug build
+ Android armv7 API 11+ ash l10n nightly-1
+ Android armv7 API 11+ ash l10n nightly-2
+ Android armv7 API 11+ ash l10n nightly-3
+ Android armv7 API 11+ ash l10n nightly-4
+ Android armv7 API 11+ ash l10n nightly-5
+ Android armv7 API 9 ash debug build
+ Android armv7 API 9 ash l10n nightly-1
+ Android armv7 API 9 ash l10n nightly-2
+ Android armv7 API 9 ash l10n nightly-3
+ Android armv7 API 9 ash l10n nightly-4
+ Android armv7 API 9 ash l10n nightly-5
+ Firefox ash win32 l10n nightly
+ Linux ash leak test spidermonkey_info-warnaserrdebug build
+ Linux ash pgo-build
+ Linux ash spidermonkey_info-warnaserr build
+ Linux x86-64 ash asan build
+ Linux x86-64 ash asan nightly
+ Linux x86-64 ash debug asan build
+ Linux x86-64 ash debug asan nightly
+ Linux x86-64 ash debug static analysis build
+ Linux x86-64 ash leak test spidermonkey_info-warnaserrdebug build
+ Linux x86-64 ash pgo-build
+ Linux x86-64 ash spidermonkey_info-warnaserr build
+ OS X 10.7 64-bit ash debug static analysis build
+ Ubuntu ASAN VM 12.04 x64 ash opt test cppunit
+ Ubuntu ASAN VM 12.04 x64 ash opt test crashtest
+ Ubuntu ASAN VM 12.04 x64 ash opt test jittest-1
+ Ubuntu ASAN VM 12.04 x64 ash opt test jittest-2
+ Ubuntu ASAN VM 12.04 x64 ash opt test jsreftest
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-1
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-2
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-3
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-4
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-5
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-browser-chrome-1
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-browser-chrome-2
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-browser-chrome-3
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-devtools-chrome
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-e10s-1
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-e10s-2
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-e10s-3
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-e10s-4
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-e10s-5
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-e10s-browser-chrome-1
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-e10s-browser-chrome-2
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-e10s-browser-chrome-3
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-gl
+ Ubuntu ASAN VM 12.04 x64 ash opt test mochitest-other
+ Ubuntu ASAN VM 12.04 x64 ash opt test reftest
+ Ubuntu ASAN VM 12.04 x64 ash opt test xpcshell
+ Ubuntu HW 12.04 ash pgo talos chromez
+ Ubuntu HW 12.04 ash pgo talos dromaeojs
+ Ubuntu HW 12.04 ash pgo talos g1
+ Ubuntu HW 12.04 ash pgo talos other_nol64
+ Ubuntu HW 12.04 ash pgo talos svgr
+ Ubuntu HW 12.04 ash pgo talos tp5o
+ Ubuntu HW 12.04 x64 ash pgo talos chromez
+ Ubuntu HW 12.04 x64 ash pgo talos dromaeojs
+ Ubuntu HW 12.04 x64 ash pgo talos g1
+ Ubuntu HW 12.04 x64 ash pgo talos other_l64
+ Ubuntu HW 12.04 x64 ash pgo talos svgr
+ Ubuntu HW 12.04 x64 ash pgo talos tp5o
+ Ubuntu VM 12.04 ash pgo test cppunit
+ Ubuntu VM 12.04 ash pgo test crashtest
+ Ubuntu VM 12.04 ash pgo test crashtest-e10s
+ Ubuntu VM 12.04 ash pgo test jetpack
+ Ubuntu VM 12.04 ash pgo test jittest-1
+ Ubuntu VM 12.04 ash pgo test jittest-2
+ Ubuntu VM 12.04 ash pgo test jsreftest
+ Ubuntu VM 12.04 ash pgo test marionette
+ Ubuntu VM 12.04 ash pgo test marionette-e10s
+ Ubuntu VM 12.04 ash pgo test mochitest-1
+ Ubuntu VM 12.04 ash pgo test mochitest-2
+ Ubuntu VM 12.04 ash pgo test mochitest-3
+ Ubuntu VM 12.04 ash pgo test mochitest-4
+ Ubuntu VM 12.04 ash pgo test mochitest-5
+ Ubuntu VM 12.04 ash pgo test mochitest-browser-chrome-1
+ Ubuntu VM 12.04 ash pgo test mochitest-browser-chrome-2
+ Ubuntu VM 12.04 ash pgo test mochitest-browser-chrome-3
+ Ubuntu VM 12.04 ash pgo test mochitest-devtools-chrome
+ Ubuntu VM 12.04 ash pgo test mochitest-e10s-1
+ Ubuntu VM 12.04 ash pgo test mochitest-e10s-2
+ Ubuntu VM 12.04 ash pgo test mochitest-e10s-3
+ Ubuntu VM 12.04 ash pgo test mochitest-e10s-4
+ Ubuntu VM 12.04 ash pgo test mochitest-e10s-5
+ Ubuntu VM 12.04 ash pgo test mochitest-e10s-browser-chrome-1
+ Ubuntu VM 12.04 ash pgo test mochitest-e10s-browser-chrome-2
+ Ubuntu VM 12.04 ash pgo test mochitest-e10s-browser-chrome-3
+ Ubuntu VM 12.04 ash pgo test mochitest-e10s-devtools-chrome
+ Ubuntu VM 12.04 ash pgo test mochitest-gl
+ Ubuntu VM 12.04 ash pgo test mochitest-other
+ Ubuntu VM 12.04 ash pgo test reftest-1
+ Ubuntu VM 12.04 ash pgo test reftest-2
+ Ubuntu VM 12.04 ash pgo test reftest-e10s
+ Ubuntu VM 12.04 ash pgo test reftest-no-accel
+ Ubuntu VM 12.04 ash pgo test web-platform-tests-1
+ Ubuntu VM 12.04 ash pgo test web-platform-tests-2
+ Ubuntu VM 12.04 ash pgo test web-platform-tests-3
+ Ubuntu VM 12.04 ash pgo test web-platform-tests-4
+ Ubuntu VM 12.04 ash pgo test web-platform-tests-reftests
+ Ubuntu VM 12.04 ash pgo test xpcshell
+ Ubuntu VM 12.04 x64 ash pgo test cppunit
+ Ubuntu VM 12.04 x64 ash pgo test crashtest
+ Ubuntu VM 12.04 x64 ash pgo test crashtest-e10s
+ Ubuntu VM 12.04 x64 ash pgo test jetpack
+ Ubuntu VM 12.04 x64 ash pgo test jittest-1
+ Ubuntu VM 12.04 x64 ash pgo test jittest-2
+ Ubuntu VM 12.04 x64 ash pgo test jsreftest
+ Ubuntu VM 12.04 x64 ash pgo test marionette
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-1
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-2
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-3
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-4
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-5
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-browser-chrome-1
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-browser-chrome-2
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-browser-chrome-3
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-devtools-chrome
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-e10s-1
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-e10s-2
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-e10s-3
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-e10s-4
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-e10s-5
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-e10s-browser-chrome-1
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-e10s-browser-chrome-2
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-e10s-browser-chrome-3
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-e10s-devtools-chrome
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-gl
+ Ubuntu VM 12.04 x64 ash pgo test mochitest-other
+ Ubuntu VM 12.04 x64 ash pgo test reftest
+ Ubuntu VM 12.04 x64 ash pgo test reftest-e10s
+ Ubuntu VM 12.04 x64 ash pgo test web-platform-tests-1
+ Ubuntu VM 12.04 x64 ash pgo test web-platform-tests-2
+ Ubuntu VM 12.04 x64 ash pgo test web-platform-tests-3
+ Ubuntu VM 12.04 x64 ash pgo test web-platform-tests-4
+ Ubuntu VM 12.04 x64 ash pgo test web-platform-tests-reftests
+ Ubuntu VM 12.04 x64 ash pgo test xpcshell
+ WINNT 5.2 ash pgo-build
+ WINNT 6.1 x86-64 ash pgo-build
+ Windows 7 32-bit ash pgo talos chromez
+ Windows 7 32-bit ash pgo talos dromaeojs
+ Windows 7 32-bit ash pgo talos g1
+ Windows 7 32-bit ash pgo talos other_nol64
+ Windows 7 32-bit ash pgo talos svgr
+ Windows 7 32-bit ash pgo talos tp5o
+ Windows 7 32-bit ash pgo talos xperf
+ Windows 7 32-bit ash pgo test cppunit
+ Windows 7 32-bit ash pgo test crashtest
+ Windows 7 32-bit ash pgo test jetpack
+ Windows 7 32-bit ash pgo test jittest
+ Windows 7 32-bit ash pgo test jsreftest
+ Windows 7 32-bit ash pgo test marionette
+ Windows 7 32-bit ash pgo test mochitest-1
+ Windows 7 32-bit ash pgo test mochitest-2
+ Windows 7 32-bit ash pgo test mochitest-3
+ Windows 7 32-bit ash pgo test mochitest-4
+ Windows 7 32-bit ash pgo test mochitest-5
+ Windows 7 32-bit ash pgo test mochitest-browser-chrome-1
+ Windows 7 32-bit ash pgo test mochitest-browser-chrome-2
+ Windows 7 32-bit ash pgo test mochitest-browser-chrome-3
+ Windows 7 32-bit ash pgo test mochitest-devtools-chrome
+ Windows 7 32-bit ash pgo test mochitest-e10s-browser-chrome-1
+ Windows 7 32-bit ash pgo test mochitest-e10s-browser-chrome-2
+ Windows 7 32-bit ash pgo test mochitest-e10s-browser-chrome-3
+ Windows 7 32-bit ash pgo test mochitest-gl
+ Windows 7 32-bit ash pgo test mochitest-other
+ Windows 7 32-bit ash pgo test reftest
+ Windows 7 32-bit ash pgo test reftest-no-accel
+ Windows 7 32-bit ash pgo test web-platform-tests-1
+ Windows 7 32-bit ash pgo test web-platform-tests-2
+ Windows 7 32-bit ash pgo test web-platform-tests-3
+ Windows 7 32-bit ash pgo test web-platform-tests-4
+ Windows 7 32-bit ash pgo test web-platform-tests-reftests
+ Windows 7 32-bit ash pgo test xpcshell
+ Windows 8 64-bit ash pgo talos chromez
+ Windows 8 64-bit ash pgo talos dromaeojs
+ Windows 8 64-bit ash pgo talos g1
+ Windows 8 64-bit ash pgo talos other_nol64
+ Windows 8 64-bit ash pgo talos svgr
+ Windows 8 64-bit ash pgo talos tp5o
+ Windows 8 64-bit ash pgo test cppunit
+ Windows 8 64-bit ash pgo test crashtest
+ Windows 8 64-bit ash pgo test jetpack
+ Windows 8 64-bit ash pgo test jittest
+ Windows 8 64-bit ash pgo test jsreftest
+ Windows 8 64-bit ash pgo test marionette
+ Windows 8 64-bit ash pgo test mochitest-1
+ Windows 8 64-bit ash pgo test mochitest-2
+ Windows 8 64-bit ash pgo test mochitest-3
+ Windows 8 64-bit ash pgo test mochitest-4
+ Windows 8 64-bit ash pgo test mochitest-5
+ Windows 8 64-bit ash pgo test mochitest-browser-chrome-1
+ Windows 8 64-bit ash pgo test mochitest-browser-chrome-2
+ Windows 8 64-bit ash pgo test mochitest-browser-chrome-3
+ Windows 8 64-bit ash pgo test mochitest-devtools-chrome
+ Windows 8 64-bit ash pgo test mochitest-e10s-browser-chrome-1
+ Windows 8 64-bit ash pgo test mochitest-e10s-browser-chrome-2
+ Windows 8 64-bit ash pgo test mochitest-e10s-browser-chrome-3
+ Windows 8 64-bit ash pgo test mochitest-gl
+ Windows 8 64-bit ash pgo test mochitest-other
+ Windows 8 64-bit ash pgo test reftest
+ Windows 8 64-bit ash pgo test reftest-no-accel
+ Windows 8 64-bit ash pgo test web-platform-tests-1
+ Windows 8 64-bit ash pgo test web-platform-tests-2
+ Windows 8 64-bit ash pgo test web-platform-tests-3
+ Windows 8 64-bit ash pgo test web-platform-tests-4
+ Windows 8 64-bit ash pgo test web-platform-tests-reftests
+ Windows 8 64-bit ash pgo test xpcshell
+ Windows XP 32-bit ash pgo talos chromez
+ Windows XP 32-bit ash pgo talos g1
+ Windows XP 32-bit ash pgo talos other_nol64
+ Windows XP 32-bit ash pgo talos svgr
+ Windows XP 32-bit ash pgo talos tp5o
+ Windows XP 32-bit ash pgo test cppunit
+ Windows XP 32-bit ash pgo test crashtest
+ Windows XP 32-bit ash pgo test jetpack
+ Windows XP 32-bit ash pgo test jittest
+ Windows XP 32-bit ash pgo test jsreftest
+ Windows XP 32-bit ash pgo test marionette
+ Windows XP 32-bit ash pgo test mochitest-1
+ Windows XP 32-bit ash pgo test mochitest-2
+ Windows XP 32-bit ash pgo test mochitest-3
+ Windows XP 32-bit ash pgo test mochitest-4
+ Windows XP 32-bit ash pgo test mochitest-5
+ Windows XP 32-bit ash pgo test mochitest-browser-chrome-1
+ Windows XP 32-bit ash pgo test mochitest-browser-chrome-2
+ Windows XP 32-bit ash pgo test mochitest-browser-chrome-3
+ Windows XP 32-bit ash pgo test mochitest-devtools-chrome
+ Windows XP 32-bit ash pgo test mochitest-gl
+ Windows XP 32-bit ash pgo test mochitest-other
+ Windows XP 32-bit ash pgo test reftest
+ Windows XP 32-bit ash pgo test web-platform-tests-1
+ Windows XP 32-bit ash pgo test web-platform-tests-2
+ Windows XP 32-bit ash pgo test web-platform-tests-3
+ Windows XP 32-bit ash pgo test web-platform-tests-4
+ Windows XP 32-bit ash pgo test web-platform-tests-reftests
+ Windows XP 32-bit ash pgo test xpcshell
Builders removed
- linux64-sh-haz_ash_dep
Attachment #8553360 - Flags: review?(rail)
Attachment #8553360 - Flags: review?(rail) → review+
I've got a 'default -> production' conflict with http://hg.mozilla.org/build/buildbot-configs/rev/4a0303d403f1 patch. I suspect it was due to a graft backout in both prod and default: http://hg.mozilla.org/build/buildbot-configs/rev/8d723094f983 and then a new patch within the same context lines before merging the branches.

either way, I will be taking whatever is on default unless I'm told otherwise.

armen, it's hard with mgerva gone but I wanted to sanity check that 1) you need l10n on ash and 2) I think this line http://hg.mozilla.org/build/buildbot-configs/annotate/0311ab1bdd95/mozilla/project_branches.py#l98 enables l10n already on its own. IIRC, it enables l10n via mh and doesn't require any of the other old items like 'enable_l10n' (things that are used for old buildbot factory l10n jobs). So do you want mh l10n which is not enabled in any prod branch outside of ash or do you want bbot factory l10n jobs?
^ re: comment 13
Flags: needinfo?(armenzg)
Landed https://hg.mozilla.org/build/buildbot-configs/rev/08c1d33c0b41 to disable l10n mozharness repacks.
Flags: needinfo?(armenzg)
buildbot-config patches are live in production
Worked locally.
Attachment #8555287 - Flags: review?(rail)
Attachment #8553360 - Flags: checked-in+
Attachment #8555287 - Flags: review?(rail) → review+
Comment on attachment 8551374 [details] [diff] [review]
Add mozharness pinning to fx-team

http://hg.mozilla.org/build/buildbot-configs/rev/dff67c5a2b57
Attachment #8551374 - Flags: checked-in- → checked-in+
(In reply to Armen Zambrano - Automation & Tools Engineer (:armenzg) from comment #12)
> https://hg.mozilla.org/build/buildbot-configs/rev/4a0303d403f1

I'm done with Ash and I'm resetting it in bug 1126433.
Attached patch pinning_mc.diffSplinter Review
If nothing crops up today with fx-team, we could enable it for m-c either Thursday or Monday.
Attachment #8555876 - Flags: review?(rail)
Attachment #8555876 - Flags: review?(rail) → review+
Blocks: 1127068
Comment on attachment 8555876 [details] [diff] [review]
pinning_mc.diff

https://hg.mozilla.org/build/buildbot-configs/rev/4b697569effd

I will notify sheriffs as I did when we enabled it for the fx-team.
Attachment #8555876 - Flags: checked-in+
The nightly builds seem to be running properly with repository_manifest.py [1]

I've started thinking that we should fix the issue where we can have someone request a build which could come without specifying a revision. If there is no revision, then we would not be able to make a substitution for manifest_url (think of %(revision)s [2]).

rail, can sheriffs trigger a nightly jobs without a property being set?

[1]
bash -c 'python /tools/checkouts/build-tools/buildfarm/utils/repository_manifest.py --default-repo https://hg.mozilla.org/build/mozharness --default-revision production --default-checkout /tools/checkouts/mozharness --checkout /builds/slave/m-cen-lx-ntly-0000000000000000/scripts --manifest-url https://hg.mozilla.org/mozilla-central/raw-file/d7e156a7a0a6d050119885d972b048c09d267e74/testing/mozharness/mozharness.json'
...
script_repo_url: https://hg.mozilla.org/build/mozharness
script_repo_revision: production
script_repo_checkout: /tools/checkouts/mozharness
program finished with exit code 0

[2]
     BRANCHES[branch]['script_repo_manifest'] = \
         "https://hg.mozilla.org/%(repo_path)s/raw-file/%(revision)s/" + \
             "testing/mozharness/mozharness.json"
> rail, can sheriffs trigger a nightly jobs without a property being set?

It seems like we can't even if self-serve can submit the form with a blank revision.

On Ash (kind of; read note [1]):
* I cannot trigger a dep build without a revision
** https://secure.pub.build.mozilla.org/buildapi/self-serve/ash/rev
** "404 Not Found\nThe resource could not be found."
* I can trigger a PGO without a revision
** https://secure.pub.build.mozilla.org/buildapi/self-serve/ash/rev//pgo
* I can trigger a nightly without a revision
** https://secure.pub.build.mozilla.org/buildapi/self-serve/ash/rev//nightly

[1] I reset Ash to be a normal tree so the PGO and nightly builders are not really there for the scheduled tasks

If we look at the pending and running jobs:
https://secure.pub.build.mozilla.org/buildapi/self-serve/ash

We can see that buildapi has scheduled *normal* build jobs that are trying to use the "pgo" and "nightly" revisions which looks like a bug in buildapi which allows feeding garbage to the wrong builders.

In other words, there is no issue for repository_manifest.py thanks to the bug in buildapi.
If by tomorrow we don't have any issues we can land this.

M-C has been running well since Friday.
Attachment #8558134 - Flags: review?(rail)
Comment on attachment 8558134 [details] [diff] [review]
Pinning trunk trees

Review of attachment 8558134 [details] [diff] [review]:
-----------------------------------------------------------------

::: mozilla-tests/b2g_config.py
@@ +2311,5 @@
>  BRANCHES['try']['enable_try'] = True
>  BRANCHES['gaia-try']['repo_path'] = "integration/gaia-try"
>  
>  # Enable mozharness pinning
> +for name, branch in items_at_least(BRANCHES, 'gecko_version', 38):

Can you replace "name" with "_", it's not used in the loop.

::: mozilla-tests/config.py
@@ +1906,5 @@
>  BRANCHES['mozilla-inbound']['platforms']['linux']['ubuntu32_vm']['debug_unittest_skipcount'] = 2
>  BRANCHES['mozilla-inbound']['platforms']['linux']['ubuntu32_vm']['debug_unittest_skiptimeout'] = 1800
>  
>  # Enable mozharness pinning
> +for name, branch in items_at_least(BRANCHES, 'gecko_version', 38):

the same here

::: mozilla-tests/mobile_config.py
@@ +1715,5 @@
>  # Until we green out these Android x86 tests
>  BRANCHES['cedar']['platforms']['android-x86']['ubuntu64_hw']['opt_unittest_suites'] += ANDROID_X86_NOT_GREEN_DICT[:]
>  
>  # Enable mozharness pinning
> +for name, branch in items_at_least(BRANCHES, 'gecko_version', 38):

and here

::: mozilla/config.py
@@ +2763,5 @@
>      # Disable symbol upload across the board
>      BRANCHES['try']['platforms'][platform]['upload_symbols'] = False
>  
>  # Enable mozharness pinning
> +for name, branch in items_at_least(BRANCHES, 'gecko_version', 38):

and here :)
Attachment #8558134 - Flags: review?(rail) → review+
Attached patch b2g_pinning.diffSplinter Review
We somehow missed b2g builds :/
Attachment #8558754 - Flags: review?(rail)
Attachment #8558754 - Flags: review?(rail) → review+
Attachment #8558134 - Flags: checked-in+
Attachment #8558754 - Flags: checked-in+
Attachment #8561383 - Flags: review?(rail) → review+
Comment on attachment 8561383 [details] [diff] [review]
[bc] remaining trees -- b2g_builds up to m-c, b2g-i and fx-team

https://hg.mozilla.org/build/buildbot-configs/rev/92bac9ad80b6

Waiting on reconfig.
Attachment #8561383 - Flags: checked-in+
This is the last of the changes.
After this one we can pin all the trees.
Attachment #8563385 - Flags: review?(rail)
Attachment #8563385 - Flags: review?(rail) → review+
Time to pin all trees up to gecko 30.
I will be landing across the board.
I will coordinate with sheriffs and buildduty.
Attachment #8565525 - Flags: review?(rail)
Comment on attachment 8565525 [details] [diff] [review]
Pin to d5c3f2d98f46

stamp
Attachment #8565525 - Flags: review?(rail) → review+
No issues in the gecko trees. m-r is still running.

The b2g trees don't have issues either. Some jobs are still running.
2.1s didn't need a distinct landing either. The link below explains:
https://wiki.mozilla.org/Release_Management/B2G_Landing
https://hg.mozilla.org/mozilla-central/rev/d58b4ab4b72a
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
As long as releng keeps on merging mozharness changes from default to the production branch TB will not fall behind.
As far as I know this will not be changing in the near term.

If we don't want to figure out pinning for TB jobs we can simply start checking out the "default" branch instead of "production".
(In reply to Armen Zambrano - Automation & Tools Engineer (:armenzg) from comment #47)
> As long as releng keeps on merging mozharness changes from default to the
> production branch TB will not fall behind.
> As far as I know this will not be changing in the near term.
> 
> If we don't want to figure out pinning for TB jobs we can simply start
> checking out the "default" branch instead of "production".

Since your goal is to stop supporting old versions of the tree, not pinning TB as well is mildly scary. The problem is that the file you need to look at is not in the comm-central repository, it's only in mozilla-central repositories, so it looks hard to do without a comm-central/mozilla-central merger. :-(
Unless we add a mozharness.json file to the thunderbird trees and use that.
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.