Changed wget output log granularity from 📣 to :giga: (only used in case the python library didn't cover all usecases)
Added python methods to async cache/download all required files for update verify
Modified Dockerfile requirements to include aiohttp python lib
Differential Revision: https://phabricator.services.mozilla.com/D129429
I forgot to update the module name in the new '--diff' feature when renaming
the module to 'gecko_taskgraph'.
This syncs the commit to standalone taskgraph here:
c3b465290f
Differential Revision: https://phabricator.services.mozilla.com/D129558
esr91 should now update the regular (non-next) ESR bouncer aliases, and
update-verify should test updates from esr 68.x to 91.x.
Differential Revision: https://phabricator.services.mozilla.com/D129397
The only non-github CI change is the addition of `default-features =
false` to the error-chain dependency, which removes the need for e.g.
the object crate.
Differential Revision: https://phabricator.services.mozilla.com/D129113
Some of these values can be computed from the relevant packages and
various defaults, but the logic is sufficiently complicated that I
would prefer to have the values come directly from the YAML
configuration file. This is breaking new ground: now some
configuration depends on the `package-format`.
The existing packages like `target.installer.msix` that are signed
with the "Mozilla Corporation" key for enterprise customers have
package family name like `Mozilla.MozillaFirefox`. The new packages
that are unsigned for the Microsoft Store are named like
`target.store.msix` and have package family name like
`Mozilla.Firefox`. This allows the two to coexist on a single system,
which is most flexible and may prove useful.
Differential Revision: https://phabricator.services.mozilla.com/D128431
Some of these values can be computed from the relevant packages and
various defaults, but the logic is sufficiently complicated that I
would prefer to have the values come directly from the YAML
configuration file. This is breaking new ground: now some
configuration depends on the `package-format`.
The existing packages like `target.installer.msix` that are signed
with the "Mozilla Corporation" key for enterprise customers have
package family name like `Mozilla.MozillaFirefox`. The new packages
that are unsigned for the Microsoft Store are named like
`target.store.msix` and have package family name like
`Mozilla.Firefox`. This allows the two to coexist on a single system,
which is most flexible and may prove useful.
Differential Revision: https://phabricator.services.mozilla.com/D128431
CLOSED TREE
This patch reduces the number of browser-cycles that a live-site test (cnn in this case) does from 25 down to 5. Furthermore, we also disable media autoplay for all live site tests. This change required an update to browsertime to prevent default prefs from being set and overriding our prefs.
Differential Revision: https://phabricator.services.mozilla.com/D127831
This patch reduces the number of browser-cycles that a live-site test (cnn in this case) does from 25 down to 5. Furthermore, we also disable media autoplay for all live site tests. This change required an update to browsertime to prevent default prefs from being set and overriding our prefs.
Differential Revision: https://phabricator.services.mozilla.com/D127831
We're adding a watershed at 72.0 for beta/aurora to match release's
72.0.2 watershed (from bug 1615382). We can simplify
update-verify-config accordingly.
Differential Revision: https://phabricator.services.mozilla.com/D128101
This change adds a new lint `android-format` which enforces formatting of Java
code using google-java-format.
To run the lint simply run:
./mach lint -l android-format
This command also support automatically fixing all errors running by adding
--fix:
./mach lint -l android-format --fix
This change also removes all the formatting-related checkstyle checks which are
now implicitly enforced by the formatter.
Differential Revision: https://phabricator.services.mozilla.com/D127734
First, import `yaml` from `taskgraph` instead of `gecko_taskgraph` now
that bug 1733950 has landed.
Second, avoid trying to create decision task indexes if `gecko_taskgraph.create.testing` is True (we set this in `test-action-callback` [here](https://searchfox.org/mozilla-central/rev/d488f68d845a87cc107612b667951152c34fb116/taskcluster/gecko_taskgraph/actions/registry.py#344); we need to import `create` and check `create.testing` rather than `from create import testing` because the value changes after we import it.
Third, don't die in `optimize` if we're in testing: the `status_task` call can return `None` in that case.
And fourth, let's noop bugbug `push_schedules` if we're in `create.testing`; this appears to fix a hang.
Differential Revision: https://phabricator.services.mozilla.com/D128001
Gecko taskgraph is now an official consumer of standalone taskgraph.
I chose 'util/yaml.py' since both copies were identical. I've also synced the
test for them, so no coverage is being lost.
Depends on D127872
Differential Revision: https://phabricator.services.mozilla.com/D127873
The 'tgdiff' task can fail if you are working on the 'taskgraph' module itself
and the parent revision isn't compatible with your changes.
This ensures the 'tgdiff' task stays green if there was a failure on the
parent, but still turns orange if there was a failure on the current revision
(since that is likely a legit error)
Differential Revision: https://phabricator.services.mozilla.com/D127874
I'd like to vendor the 'taskcluster-taskgraph' pacakge, but it requires slugid
>= 2.0. In order to update that we also need to update 'taskcluster' and
'taskcluster_urls' as the currently vendored versions don't work with
'slugid>=2.0' (due to slugid returning str rather than bytes here).
Version changes are:
* taskcluster 6.0.0 -> 44.2.2
* taskcluster_urls 11.0.0 -> 13.0.1
* slugid 1.0.7 -> 2.0.0
Differential Revision: https://phabricator.services.mozilla.com/D127680
Due to having apt install "recommended packages", we're having the
`python3-gi` package installed.
However, though the *apt* package of `python3-gi` doesn't depend on
anything, the underlying Python `PyGObject` package does depend on
`pycairo`.
By installing `python3-cairo`, we resolve the missing Python package
dependency, allowing `pip check` to complete successfully.
Differential Revision: https://phabricator.services.mozilla.com/D127458
For a long time two copies of the 'taskgraph' module have existed in parallel.
We've attempted to keep them in sync, but over time they have diverged and the
maintenance burden has increased.
In order to reduce this burden, we'd like to re-join the two code bases. The
canonical repo will be the one that lives outside of mozilla-central, and this
module will depend on it. Since they both have the same module name (taskgraph)
we need to rename the version in mozilla-central to avoid collisions.
Other consumers of 'taskgraph' (like mobile repos) have standardized on
'<project>_taskgraph' as their module names. So replicating that here as well.
Differential Revision: https://phabricator.services.mozilla.com/D127118
We used to build extra bz2-compressed mar files for ESR, but that was
removed in bug 1599223.
Also remove "linux4\b.*" entries, they don't match anything, so were
likely always meant to be linux64, but aren't necessary since the
"linux.*" entry covers it.
Differential Revision: https://phabricator.services.mozilla.com/D127470
"This is nightly so we don't know what partials we need" is not the same
as "we're making a release and we know we don't want partials". In one
case (when called from get_decision_parameters) partial_updates is None,
in the other (called from release_promotion_action) it's an empty dict.
The latter case still enforces non-empty partial_updates for production,
but for staging it's not really necessary and falling back to nightly
behaviour in populate_release_history is just wrong.
Differential Revision: https://phabricator.services.mozilla.com/D127228
GNOME Software 41 displays the developer_name very prominently on an
app's listing. Previously Firefox did not set one.
The summary should not repeat the app's name, but (quoting the spec)
should be "A short summary of what this component does".
Differential Revision: https://phabricator.services.mozilla.com/D126583