Bug 1336559 - Rename source-check kind to source-test, r=dustin

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
This commit is contained in:
Andrew Halberstadt 2017-02-02 16:16:06 -05:00
Родитель eb5ac7c85b
Коммит 2d476494f7
7 изменённых файлов: 6 добавлений и 6 удалений

Просмотреть файл

Просмотреть файл

@ -50,13 +50,13 @@ passes them to signing servers to have their contents signed appropriately, base
on an appropriate signing format. One signing job is created for each nightly-l10n
job (usually chunked).
source-check
source-test
------------
Source-checks are tasks that look at the Gecko source directly to check
correctness. This can include linting, Python unit tests, source-code
analysis, or measurement work -- basically anything that does not require a
build.
Source-tests are tasks that run directly from the Gecko source. This can include linting,
unit tests, source-code analysis, or measurement work. While source-test tasks run from
a source checkout, it is still possible for them to depend on a build artifact, though
often they do not.
upload-symbols
--------------

Просмотреть файл

@ -35,7 +35,7 @@ BUILD_KINDS = set([
# anything in this list is governed by -j
JOB_KINDS = set([
'source-check',
'source-test',
'toolchain',
'marionette-harness',
'android-stuff',