зеркало из https://github.com/mozilla/gecko-dev.git
6e7426cf02
There are now Buildbot jobs which can be triggered via the Buildbot Bridge. Buildbot test jobs triggered by BBB builds do not receive the installer and test urls with a sendchange, hence, failling to run. In order to pass the installer and test urls to Buildbot test jobs triggered via BBB (which run with --read-buildbot-configs) we have added functionality to find these build artifacts by querying TaskCluster. Up until last quarter this worked because the Buildbot Bridge uploaded a proprties.json file for every task it created to mirror a Buildbot job (bug 1221091). Since that is broken, I have found that we can generate a buildbot_properties.json file and upload it. The current upload mechanism for Buildbot build jobs is that it creates a TC task and uploads the artifacts there. In this code change, we determine when a Buildbot job is being driven by a task on TC (aka BBB) and tell the upload system to use that task instead of creating a new one. By doing that, tools like Mozilla CI tools can schedule TC graphs out of band by specifying 'parent_task_id' and getting to the buildbot_properties.json file uploaded by the parent build job. --HG-- extra : commitid : 20XrR5whTms extra : histedit_source : 2f41ffcd33ea7bb0a1fca1c95f92a2c4218b803e%2C7806527c93fc234daf87fa2c704138d4cd368cca |
||
|---|---|---|
| .. | ||
| configs | ||
| docs | ||
| examples | ||
| external_tools | ||
| mozfile | ||
| mozharness | ||
| mozinfo | ||
| mozprocess | ||
| scripts | ||
| test | ||
| LICENSE | ||
| README.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
| unit.sh | ||
README.txt
# Mozharness ### Submitting changes Like any Gecko change, please create a patch or submit to Mozreview and open a Bugzilla ticket under the Mozharness component: https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Mozharness This bug will get triaged by Release Engineering ### Docs * https://developer.mozilla.org/en-US/docs/Mozharness_FAQ * https://wiki.mozilla.org/ReleaseEngineering/Mozharness * http://moz-releng-mozharness.readthedocs.org/en/latest/mozharness.mozilla.html * http://moz-releng-docs.readthedocs.org/en/latest/software.html#mozharness ### To run mozharness unit tests ``` pip install tox tox # from within the $gecko_repo/testing/mozharness directory ``` Happy contributing! =)