mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-27 06:43:32 +00:00
2d476494f7
The name 'source-check' is a bit of a misnomer, because it already includes a bunch of tasks that are proper unittests, not lints. Some of these unittests will soon depend on a build task, which makes 'source-check' feel even more wrong. They still have a lot in common with the lint tasks though, so it's probably not worth splitting this into two separate kinds. Instead, let's just rename this kind to 'source-test', which means, any task that tests stuff and is run from the source directory (instead of a tests.zip). I think both lints and python-tests fall squarely under this definition. MozReview-Commit-ID: K0gZ5rVLyeD --HG-- rename : taskcluster/ci/source-check/doc.yml => taskcluster/ci/source-test/doc.yml rename : taskcluster/ci/source-check/kind.yml => taskcluster/ci/source-test/kind.yml rename : taskcluster/ci/source-check/mozlint.yml => taskcluster/ci/source-test/mozlint.yml rename : taskcluster/ci/source-check/python-tests.yml => taskcluster/ci/source-test/python-tests.yml rename : taskcluster/ci/source-check/webidl.yml => taskcluster/ci/source-test/webidl.yml extra : rebase_source : a683b5b6e243849de57f2681993046c776d6a8f2 |
||
|---|---|---|
| .. | ||
| action-spec.rst | ||
| actions-schema.yml | ||
| attributes.rst | ||
| caches.rst | ||
| cron.rst | ||
| docker-images.rst | ||
| how-tos.rst | ||
| in-tree-actions.rst | ||
| index.rst | ||
| kinds.rst | ||
| loading.rst | ||
| parameters.rst | ||
| reference.rst | ||
| taskgraph.rst | ||
| transforms.rst | ||
| yaml-templates.rst | ||