| __init__.py |
Returns relpath with 'comm/' prefix removed.
:param string relpath: relative path
:return string: stripped path
|
467 |
- |
| docker.py |
|
644 |
- |
| hash.py |
Give a list of path patterns and return two lists. rv[0] corresponds to files from the
GECKO repository, rv[1] corresponds to COMM.
The pattern list for the COMM repository will have *not* the 'comm/' prefix stripped.
|
2500 |
- |
| l10n.py |
Parse the passed locales file for a list of locales, exclude ja-JP-mac. |
467 |
- |
| partners.py |
|
754 |
- |
| shippable_repacks.py |
Schedule the Thunderbird Enterprise shippable builds and repacks at most
once a day per branch.
TODO: Remove this module once Thunderbird Enterprise schedules its repacks
through the release promotion action, as Firefox Enterprise does.
Until then, nothing asks for the repacks: every level 3 push schedules the
shippable builds, the repacks made from them and their OCI uploads, which is
costly and races between pushes. The first push of each UTC day on a branch
schedules them, and marks it in the index (see
`get_shippable_repacks_produced_index`). Later pushes on that day find the
entry and skip them.
The entry is inserted as soon as the decision task chooses to schedule them,
long before they are created, let alone completed: despite its name, it means
"scheduled". This leaves only a short window for two decision tasks to both
schedule them, as the index offers no atomic way to claim an entry.
The entry points to the decision task that inserted it, and is ignored when that
task failed, so the next push schedules them again. To schedule them again
anyway, e.g. to ship a fix the same day, delete the entry with
`index.deleteTask`, which requires the
`index:delete-task:<index path>` scope, then push or rerun the decision task.
|
5616 |
- |
| suite.py |
|
544 |
- |
| taskgraph_attributes.py |
This file contains the constants from gecko_taskgraph.util.attributes, but
only the Thunderbird repositories are included.
|
4281 |
- |
| verify.py |
Projects that make use of Firefox's taskgraph can extend it with
their own task kinds by registering additional paths for documentation.
documentation_paths.add() needs to be called by the project's Taskgraph
registration function. See taskgraph.config.
|
25555 |
- |