Mozci (Mozilla CI tools) is a python library, scripts and package which allows you to trigger jobs on treeherder.mozilla.org.
Not all jobs can be triggered but those that are run on Release Engineering's Buildbot setup. Most (if not all) Firefox desktop and Firefox for Android jobs can be triggered. I believe some B2G jobs can still be triggered.
NOTE: Most B2G jobs are not supported yet since they run on TaskCluster. Support for it will be given on this quarter.
Mozci (Mozilla CI tools) is a python library, scripts and package which allows you to trigger jobs on treeherder.mozilla.org.Not all jobs can be triggered but those that are run on Release Engineering's Buildbot setup. Most (if not all) Firefox desktop and Firefox for Android jobs can be triggered. I believe some B2G jobs can still be triggered.
NOTE: Most B2G jobs are not supported yet since they run on TaskCluster. Support for it will be given on this quarter.
Using it
Once you check out the code:git clone https://github.com/armenzg/mozilla_ci_tools.gityou can run scripts like this one (click here for other scripts):
python setup.py develop
python scripts/trigger.py \which would trigger a specific job 10 times.
--buildername "Rev5 MacOSX Yosemite 10.10 fx-team talos dromaeojs" \
--rev e16054134e12 --times 10
NOTE: This is independent if a build job exist to trigger the test job. mozci will trigger everything which is required to get you what you need.
One of the many other options is if you want to trigger the same job for the last X revisions, this would require you to use --back-revisions X.
There are many use cases and options listed in here.
A use case for developers
One use case which could be useful to developers (thanks @mike_conley!) is if you pushed to try and used this try syntax: "try: -b o -p win32 -u mochitests -t none". Unfortunately, you later determine that you really need this one: "try: -b o -p linux64,macosx64,win32 -u reftest,mochitests -t none".
In normal circumstances you would go and push again to the try server, however, with mozci (once someone implements this), we could simply pass the new syntax to a script (or with ./mach) and trigger everything that you need rather than having to push again and waster resources and your time!
If you have other use cases, please file an issue in here.
If you want to read about the definition of the project, vision, use cases or FAQ please visit the documentation.
This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
Not all jobs can be triggered but those that are run on Release Engineering's Buildbot setup. Most (if not all) Firefox desktop and Firefox for Android jobs can be triggered. I believe some B2G jobs can still be triggered.
NOTE: Most B2G jobs are not supported yet since they run on TaskCluster. Support for it will be given on this quarter.
Using it
Once you check out the code:git clone https://github.com/armenzg/mozilla_ci_tools.gityou can run scripts like this one (click here for other scripts):
python setup.py develop
python scripts/trigger.py \which would trigger a specific job 10 times.
--buildername "Rev5 MacOSX Yosemite 10.10 fx-team talos dromaeojs" \
--rev e16054134e12 --times 10
NOTE: This is independent if a build job exist to trigger the test job. mozci will trigger everything which is required to get you what you need.
One of the many other options is if you want to trigger the same job for the last X revisions, this would require you to use --back-revisions X.
There are many use cases and options listed in here.
A use case for developers
One use case which could be useful to developers (thanks @mike_conley!) is if you pushed to try and used this try syntax: "try: -b o -p win32 -u mochitests -t none". Unfortunately, you later determine that you really need this one: "try: -b o -p linux64,macosx64,win32 -u reftest,mochitests -t none".
In normal circumstances you would go and push again to the try server, however, with mozci (once someone implements this), we could simply pass the new syntax to a script (or with ./mach) and trigger everything that you need rather than having to push again and waster resources and your time!
If you have other use cases, please file an issue in here.
If you want to read about the definition of the project, vision, use cases or FAQ please visit the documentation.
This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
by Jillur Rahman
Jillur Rahman is a Web designers. He enjoys to make blogger templates. He always try to make modern and 3D looking Templates. You can by his templates from Themeforest.
Follow him @ Twitter | Facebook | Google Plus
No Comment