Run ci-admin/ci-config/taskgraphs's unit tests and lint as part of the phabricator review process
Categories
(Developer Infrastructure :: Source Code Analysis, enhancement)
Tracking
(Not tracked)
People
(Reporter: dustin, Assigned: tomprince)
References
Details
Attachments
(15 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
These are basic Python things, nothing fancy. python setup.py test python setup.py flake8
Comment 1•6 years ago
|
||
This is a good idea. We currently only support mozilla-central, but we can figure out how to support other projects too (not only ci-admin, but for example NSS too). I've filed https://github.com/mozilla/release-services/issues/1511.
Comment 2•5 years ago
|
||
Hi Kim,
Is this something your team would like to pick up?
Thanks,
Pete
Comment 3•5 years ago
|
||
I talked to Steven about this and he said that Sylvestre's team has a bot that polls lando to run linting tests. This is not within the scope of our tools.
Comment 4•5 years ago
|
||
Pete, we have been discussing about extending our tools to other project.
I think we should start a discussion on how to implement that in a scalable way.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
Reviewbot uses try_task_config to pass information about what phabricator diff
is being checked via this file, so add support for getting info from it.
Updated•4 years ago
|
Assignee | ||
Comment 6•4 years ago
|
||
This different from the one in mozilla-central, as it uses a morph to generate
the code-review task. This makes it easier for downstream projects, as they
will not need to add boilerplate kind to generate the task.
Assignee | ||
Comment 7•4 years ago
|
||
Assignee | ||
Comment 8•4 years ago
|
||
ci-admin check
changes the working directory, to make pytest work. If the
--ci-configuration-directory
is not absolute, it won't be found after
changing directory. Ask click to make it absolute for us, when parsing the
command-line.
Assignee | ||
Comment 9•4 years ago
|
||
This enables using the same taskgraph config for both ci-admin and
ci-configuration.
Assignee | ||
Comment 10•4 years ago
|
||
Assignee | ||
Comment 11•4 years ago
|
||
Assignee | ||
Comment 12•4 years ago
|
||
This means that configuration will be kept in sync, and it will also pick up
the code-review configuration.
Updated•4 years ago
|
Assignee | ||
Comment 13•4 years ago
|
||
When checking out multiple repos, robustcheckout won't cleanup
sub-repositories, so include the layout in the cache name.
Assignee | ||
Comment 14•4 years ago
|
||
When I first setup the non-gecko taskgraph, I imagined that we would
use a docker image with taskgraph pre-installed. However, rather than
dealing with the implications of chain-of-trust for those images, we
ended up installing taskgraph at runtime. ci-admin pre-dates that change. In
the interest of keeping things aligned, this switches ci-admin to install
taskgraph at runtime.
Assignee | ||
Comment 15•4 years ago
|
||
ci-admin and ci-config share a taskgraph configuration. Since ci-config only
contains the taskcluster configuration, there is not a need for it to have it's
own .taskcluster.yml
. This adds support to ci-admin to specify that a project uses
a .taskcluster.yml
from another repository.
Assignee | ||
Comment 16•4 years ago
|
||
Assignee | ||
Comment 17•4 years ago
|
||
When I first setup the non-gecko taskgraph, I imagined that we would use a
docker image with taskgraph pre-installed. However, rather than dealing with
the implications of chain-of-trust for those images, we ended up installing
taskgraph at runtime. This removes the now unused image.
Assignee | ||
Comment 18•4 years ago
|
||
This also adjust the hg-push task to pass the required environment variables through.
Assignee | ||
Comment 19•4 years ago
|
||
Now that ci-configuration is using a .taskcluster.yml
from ci-admin, we can
remove the .taskcluster.yml
from ci-configuration.
Assignee | ||
Updated•4 years ago
|
Updated•2 years ago
|
Description
•