| commit | 308322dff5d262b87007fa158776527682b6ae7b | |
| author | Andrew Halberstadt <ahal@mozilla.com> | |
| Thu, 10 Mar 2022 20:52:24 +0000 (10 15:52 -0500) | ||
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | |
| Fri, 18 Mar 2022 15:55:53 +0000 (18 15:55 +0000) | ||
| tree | 5ff5d5264505606e2a2cc9ce2a2d4c9e51bf8798 | treesnapshot (tar.gz zip) |
| parent | 5d44ff45fd7fb1fd3d9796d408666136414dd561 | commitdiff |
[components] Bootstrap Taskgraph from pypi in decision task
Releng has tweaked the recommended way of bootstrapping Taskgraph from a
clone + checkout pinned revision, to Pypi and a requirements.txt.
This provides a few benefits:
1. Since Taskgraph uses SemVer, updating will provide a hint if there
will be backwards incompatible changes.
2. Using version numbers is nicer than revisions (e.g, Taskgraph's
CHANGELOG will be useful).
3. Provides a mechanism to pin other non-Taskgraph dependencies.
The reason I'm submitting this now is I'd like to migrate Taskgraph to a
new repository. By moving consumers over to Pypi first, the migration
can happen seamlessly without breaking anything.
Jira: RELENG-806
Releng has tweaked the recommended way of bootstrapping Taskgraph from a
clone + checkout pinned revision, to Pypi and a requirements.txt.
This provides a few benefits:
1. Since Taskgraph uses SemVer, updating will provide a hint if there
will be backwards incompatible changes.
2. Using version numbers is nicer than revisions (e.g, Taskgraph's
CHANGELOG will be useful).
3. Provides a mechanism to pin other non-Taskgraph dependencies.
The reason I'm submitting this now is I'd like to migrate Taskgraph to a
new repository. By moving consumers over to Pypi first, the migration
can happen seamlessly without breaking anything.
Jira: RELENG-806