2016-10-26 23:18:24 +03:00
|
|
|
# This Source Code Form is subject to the terms of the Mozilla Public
|
|
|
|
|
# License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
|
|
|
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
|
|
|
|
|
|
2017-08-02 12:02:44 +03:00
|
|
|
linux64-clang-3.9:
|
|
|
|
|
description: "Clang 3.9 toolchain build"
|
2016-10-26 23:18:24 +03:00
|
|
|
treeherder:
|
|
|
|
|
kind: build
|
Bug 1338061 - Move toolchain tasks to a separate "platform". r=dustin
The toolchain tasks are hard to spot on treeherder, in the ocean of
build and test jobs associated with the platforms they are currently
under.
Now that we have a significant number of toolchain tasks across
different platforms, it's even worse, especially combined with the fact
that they don't happen on every push.
To make them more easily visible, we move them to a new, separate,
"platform", with the name "toolchains", instead of having them in
different platforms. But since the distinction between Linux, OSX and
Windows 32/64 is still interesting to have, we create groups for each of
those platforms.
But because of bug 1215587, the jobs still end up associated to their
previous group, defeating the new grouping, so to work around that bug,
we also rename the jobs in subtle ways.
--HG--
extra : rebase_source : 6c093c070c18a64eba1c21bf2a2c97b2a9aaabc5
2017-01-27 05:46:22 +03:00
|
|
|
platform: toolchains/opt
|
2017-08-02 12:02:44 +03:00
|
|
|
symbol: TL(clang3.9)
|
2016-10-26 23:18:24 +03:00
|
|
|
tier: 1
|
|
|
|
|
worker-type: aws-provisioner-v1/gecko-{level}-b-linux
|
|
|
|
|
worker:
|
|
|
|
|
docker-image: {in-tree: desktop-build}
|
|
|
|
|
max-run-time: 36000
|
2017-02-01 03:27:31 +03:00
|
|
|
run:
|
|
|
|
|
using: toolchain-script
|
2017-08-02 12:02:44 +03:00
|
|
|
script: build-clang-3.9-linux.sh
|
2017-02-01 03:27:31 +03:00
|
|
|
resources:
|
Bug 1386588 - Avoid wildcards in toolchain resources lists. r=gps
Those resources are used to compute a unique identifier for the
toolchain, and changes to those files will change the unique identifier,
and lead to the toolchain being rebuilt.
Using wildcards, especially in the build-clang directory, makes all the
files from there used for the unique identifier, even files irrelevant.
The side effect is that any change to any json file for clang toolchains
currently triggers *all* clang toolchains to be rebuilt, which is a
waste of resources and time.
But while it is tempting to list all the files involved, it is also
tedious and error-prone. Specifically, listing the relevant patch files
for clang toolchain builds is bound to end up outdated. OTOH, we're not
trying to mitigate bad actors here, but just to avoid shooting ourselves
in the foot. And patch files are, in practice, not changed. The jsons
are changed to reference them or not, but the patches themselves don't
change in relevant ways. They may be updated for new versions of clang,
which require a json change anyways. So we ignore the patch files.
2017-08-02 11:42:40 +03:00
|
|
|
- 'build/build-clang/build-clang.py'
|
2017-08-02 12:02:44 +03:00
|
|
|
- 'build/build-clang/clang-3.9-linux64.json'
|
2017-04-15 03:03:05 +03:00
|
|
|
- 'taskcluster/scripts/misc/tooltool-download.sh'
|
2017-08-02 12:02:44 +03:00
|
|
|
toolchain-alias: linux64-clang
|
2017-07-21 01:30:14 +03:00
|
|
|
toolchain-artifact: public/build/clang.tar.xz
|
2017-07-20 11:56:49 +03:00
|
|
|
toolchains:
|
2017-08-03 06:24:41 +03:00
|
|
|
- linux64-gcc-4.9
|
2016-10-26 23:18:24 +03:00
|
|
|
|
2017-08-02 13:53:28 +03:00
|
|
|
linux64-clang-4:
|
|
|
|
|
description: "Clang 4 toolchain build"
|
|
|
|
|
treeherder:
|
|
|
|
|
kind: build
|
|
|
|
|
platform: toolchains/opt
|
|
|
|
|
symbol: TL(clang4)
|
|
|
|
|
tier: 1
|
|
|
|
|
worker-type: aws-provisioner-v1/gecko-{level}-b-linux
|
|
|
|
|
worker:
|
|
|
|
|
docker-image: {in-tree: desktop-build}
|
|
|
|
|
max-run-time: 36000
|
|
|
|
|
run:
|
|
|
|
|
using: toolchain-script
|
|
|
|
|
script: build-clang-4-linux.sh
|
|
|
|
|
resources:
|
|
|
|
|
- 'build/build-clang/build-clang.py'
|
|
|
|
|
- 'build/build-clang/clang-4-linux64.json'
|
|
|
|
|
- 'taskcluster/scripts/misc/tooltool-download.sh'
|
|
|
|
|
toolchain-artifact: public/build/clang.tar.xz
|
|
|
|
|
toolchains:
|
2017-08-03 06:24:41 +03:00
|
|
|
- linux64-gcc-4.9
|
2017-08-02 13:53:28 +03:00
|
|
|
|
2017-04-28 18:12:31 +03:00
|
|
|
linux64-clang-tidy:
|
2016-12-18 09:04:11 +03:00
|
|
|
description: "Clang-tidy build"
|
2017-01-03 05:07:20 +03:00
|
|
|
index:
|
|
|
|
|
product: static-analysis
|
|
|
|
|
job-name: linux64-clang-tidy
|
2016-12-18 09:04:11 +03:00
|
|
|
treeherder:
|
|
|
|
|
kind: build
|
Bug 1338061 - Move toolchain tasks to a separate "platform". r=dustin
The toolchain tasks are hard to spot on treeherder, in the ocean of
build and test jobs associated with the platforms they are currently
under.
Now that we have a significant number of toolchain tasks across
different platforms, it's even worse, especially combined with the fact
that they don't happen on every push.
To make them more easily visible, we move them to a new, separate,
"platform", with the name "toolchains", instead of having them in
different platforms. But since the distinction between Linux, OSX and
Windows 32/64 is still interesting to have, we create groups for each of
those platforms.
But because of bug 1215587, the jobs still end up associated to their
previous group, defeating the new grouping, so to work around that bug,
we also rename the jobs in subtle ways.
--HG--
extra : rebase_source : 6c093c070c18a64eba1c21bf2a2c97b2a9aaabc5
2017-01-27 05:46:22 +03:00
|
|
|
platform: toolchains/opt
|
|
|
|
|
symbol: TL(clang-tidy)
|
2016-12-18 09:04:11 +03:00
|
|
|
tier: 1
|
|
|
|
|
worker-type: aws-provisioner-v1/gecko-{level}-b-linux
|
|
|
|
|
worker:
|
|
|
|
|
docker-image: {in-tree: desktop-build}
|
|
|
|
|
max-run-time: 36000
|
2017-02-01 03:27:31 +03:00
|
|
|
run:
|
|
|
|
|
using: toolchain-script
|
|
|
|
|
script: build-clang-tidy-linux.sh
|
|
|
|
|
resources:
|
2016-12-18 09:04:11 +03:00
|
|
|
- 'build/clang-plugin/**'
|
Bug 1386588 - Avoid wildcards in toolchain resources lists. r=gps
Those resources are used to compute a unique identifier for the
toolchain, and changes to those files will change the unique identifier,
and lead to the toolchain being rebuilt.
Using wildcards, especially in the build-clang directory, makes all the
files from there used for the unique identifier, even files irrelevant.
The side effect is that any change to any json file for clang toolchains
currently triggers *all* clang toolchains to be rebuilt, which is a
waste of resources and time.
But while it is tempting to list all the files involved, it is also
tedious and error-prone. Specifically, listing the relevant patch files
for clang toolchain builds is bound to end up outdated. OTOH, we're not
trying to mitigate bad actors here, but just to avoid shooting ourselves
in the foot. And patch files are, in practice, not changed. The jsons
are changed to reference them or not, but the patches themselves don't
change in relevant ways. They may be updated for new versions of clang,
which require a json change anyways. So we ignore the patch files.
2017-08-02 11:42:40 +03:00
|
|
|
- 'build/build-clang/build-clang.py'
|
|
|
|
|
- 'build/build-clang/clang-tidy-linux64.json'
|
2017-04-15 03:03:05 +03:00
|
|
|
- 'taskcluster/scripts/misc/tooltool-download.sh'
|
2017-07-21 01:30:14 +03:00
|
|
|
toolchain-artifact: public/build/clang-tidy.tar.xz
|
2017-07-20 11:56:49 +03:00
|
|
|
toolchains:
|
2017-08-03 06:24:41 +03:00
|
|
|
- linux64-gcc-4.9
|
2016-12-18 09:04:11 +03:00
|
|
|
|
2017-08-02 12:02:44 +03:00
|
|
|
linux64-gcc-4.9:
|
|
|
|
|
description: "GCC 4.9 toolchain build"
|
2016-10-26 23:18:24 +03:00
|
|
|
treeherder:
|
|
|
|
|
kind: build
|
Bug 1338061 - Move toolchain tasks to a separate "platform". r=dustin
The toolchain tasks are hard to spot on treeherder, in the ocean of
build and test jobs associated with the platforms they are currently
under.
Now that we have a significant number of toolchain tasks across
different platforms, it's even worse, especially combined with the fact
that they don't happen on every push.
To make them more easily visible, we move them to a new, separate,
"platform", with the name "toolchains", instead of having them in
different platforms. But since the distinction between Linux, OSX and
Windows 32/64 is still interesting to have, we create groups for each of
those platforms.
But because of bug 1215587, the jobs still end up associated to their
previous group, defeating the new grouping, so to work around that bug,
we also rename the jobs in subtle ways.
--HG--
extra : rebase_source : 6c093c070c18a64eba1c21bf2a2c97b2a9aaabc5
2017-01-27 05:46:22 +03:00
|
|
|
platform: toolchains/opt
|
2017-08-02 12:02:44 +03:00
|
|
|
symbol: TL(gcc4.9)
|
2016-10-26 23:18:24 +03:00
|
|
|
tier: 1
|
|
|
|
|
worker-type: aws-provisioner-v1/gecko-{level}-b-linux
|
|
|
|
|
worker:
|
|
|
|
|
docker-image: {in-tree: desktop-build}
|
|
|
|
|
max-run-time: 36000
|
2017-02-01 03:27:31 +03:00
|
|
|
run:
|
|
|
|
|
using: toolchain-script
|
2017-08-02 12:02:44 +03:00
|
|
|
script: build-gcc-4.9-linux.sh
|
2017-02-01 03:27:31 +03:00
|
|
|
resources:
|
Bug 1386588 - Avoid wildcards in toolchain resources lists. r=gps
Those resources are used to compute a unique identifier for the
toolchain, and changes to those files will change the unique identifier,
and lead to the toolchain being rebuilt.
Using wildcards, especially in the build-clang directory, makes all the
files from there used for the unique identifier, even files irrelevant.
The side effect is that any change to any json file for clang toolchains
currently triggers *all* clang toolchains to be rebuilt, which is a
waste of resources and time.
But while it is tempting to list all the files involved, it is also
tedious and error-prone. Specifically, listing the relevant patch files
for clang toolchain builds is bound to end up outdated. OTOH, we're not
trying to mitigate bad actors here, but just to avoid shooting ourselves
in the foot. And patch files are, in practice, not changed. The jsons
are changed to reference them or not, but the patches themselves don't
change in relevant ways. They may be updated for new versions of clang,
which require a json change anyways. So we ignore the patch files.
2017-08-02 11:42:40 +03:00
|
|
|
- 'build/unix/build-gcc/build-gcc.sh'
|
2017-08-02 12:02:44 +03:00
|
|
|
toolchain-alias: linux64-gcc
|
2017-07-21 01:30:14 +03:00
|
|
|
toolchain-artifact: public/build/gcc.tar.xz
|
2016-10-26 23:18:24 +03:00
|
|
|
|
2017-08-02 13:43:15 +03:00
|
|
|
linux64-gcc-6:
|
|
|
|
|
description: "GCC 6 toolchain build"
|
|
|
|
|
treeherder:
|
|
|
|
|
kind: build
|
|
|
|
|
platform: toolchains/opt
|
|
|
|
|
symbol: TL(gcc6)
|
|
|
|
|
tier: 1
|
|
|
|
|
worker-type: aws-provisioner-v1/gecko-{level}-b-linux
|
|
|
|
|
worker:
|
|
|
|
|
docker-image: {in-tree: desktop-build}
|
|
|
|
|
max-run-time: 36000
|
|
|
|
|
run:
|
|
|
|
|
using: toolchain-script
|
|
|
|
|
script: build-gcc-6-linux.sh
|
|
|
|
|
resources:
|
|
|
|
|
- 'build/unix/build-gcc/build-gcc.sh'
|
|
|
|
|
toolchain-artifact: public/build/gcc.tar.xz
|
|
|
|
|
|
2017-04-28 18:12:31 +03:00
|
|
|
linux64-binutils:
|
2016-10-26 23:18:24 +03:00
|
|
|
description: "Binutils toolchain build"
|
|
|
|
|
treeherder:
|
|
|
|
|
kind: build
|
Bug 1338061 - Move toolchain tasks to a separate "platform". r=dustin
The toolchain tasks are hard to spot on treeherder, in the ocean of
build and test jobs associated with the platforms they are currently
under.
Now that we have a significant number of toolchain tasks across
different platforms, it's even worse, especially combined with the fact
that they don't happen on every push.
To make them more easily visible, we move them to a new, separate,
"platform", with the name "toolchains", instead of having them in
different platforms. But since the distinction between Linux, OSX and
Windows 32/64 is still interesting to have, we create groups for each of
those platforms.
But because of bug 1215587, the jobs still end up associated to their
previous group, defeating the new grouping, so to work around that bug,
we also rename the jobs in subtle ways.
--HG--
extra : rebase_source : 6c093c070c18a64eba1c21bf2a2c97b2a9aaabc5
2017-01-27 05:46:22 +03:00
|
|
|
platform: toolchains/opt
|
|
|
|
|
symbol: TL(binutil)
|
2016-10-26 23:18:24 +03:00
|
|
|
tier: 1
|
|
|
|
|
worker-type: aws-provisioner-v1/gecko-{level}-b-linux
|
|
|
|
|
worker:
|
|
|
|
|
docker-image: {in-tree: desktop-build}
|
|
|
|
|
max-run-time: 36000
|
2017-02-01 03:27:31 +03:00
|
|
|
run:
|
|
|
|
|
using: toolchain-script
|
|
|
|
|
script: build-binutils-linux.sh
|
|
|
|
|
resources:
|
Bug 1386588 - Avoid wildcards in toolchain resources lists. r=gps
Those resources are used to compute a unique identifier for the
toolchain, and changes to those files will change the unique identifier,
and lead to the toolchain being rebuilt.
Using wildcards, especially in the build-clang directory, makes all the
files from there used for the unique identifier, even files irrelevant.
The side effect is that any change to any json file for clang toolchains
currently triggers *all* clang toolchains to be rebuilt, which is a
waste of resources and time.
But while it is tempting to list all the files involved, it is also
tedious and error-prone. Specifically, listing the relevant patch files
for clang toolchain builds is bound to end up outdated. OTOH, we're not
trying to mitigate bad actors here, but just to avoid shooting ourselves
in the foot. And patch files are, in practice, not changed. The jsons
are changed to reference them or not, but the patches themselves don't
change in relevant ways. They may be updated for new versions of clang,
which require a json change anyways. So we ignore the patch files.
2017-08-02 11:42:40 +03:00
|
|
|
- 'build/unix/build-binutils/build-binutils.sh'
|
2017-07-21 01:30:14 +03:00
|
|
|
toolchain-artifact: public/build/binutils.tar.xz
|
2017-01-23 05:14:03 +03:00
|
|
|
|
2017-04-28 18:12:31 +03:00
|
|
|
linux64-cctools-port:
|
2017-01-23 05:14:03 +03:00
|
|
|
description: "cctools-port toolchain build"
|
|
|
|
|
treeherder:
|
|
|
|
|
kind: build
|
Bug 1338061 - Move toolchain tasks to a separate "platform". r=dustin
The toolchain tasks are hard to spot on treeherder, in the ocean of
build and test jobs associated with the platforms they are currently
under.
Now that we have a significant number of toolchain tasks across
different platforms, it's even worse, especially combined with the fact
that they don't happen on every push.
To make them more easily visible, we move them to a new, separate,
"platform", with the name "toolchains", instead of having them in
different platforms. But since the distinction between Linux, OSX and
Windows 32/64 is still interesting to have, we create groups for each of
those platforms.
But because of bug 1215587, the jobs still end up associated to their
previous group, defeating the new grouping, so to work around that bug,
we also rename the jobs in subtle ways.
--HG--
extra : rebase_source : 6c093c070c18a64eba1c21bf2a2c97b2a9aaabc5
2017-01-27 05:46:22 +03:00
|
|
|
platform: toolchains/opt
|
|
|
|
|
symbol: TL(cctools)
|
2017-01-23 05:14:03 +03:00
|
|
|
tier: 1
|
|
|
|
|
worker-type: aws-provisioner-v1/gecko-{level}-b-linux
|
|
|
|
|
worker:
|
|
|
|
|
docker-image: {in-tree: desktop-build}
|
|
|
|
|
max-run-time: 36000
|
2017-02-01 03:27:31 +03:00
|
|
|
run:
|
|
|
|
|
using: toolchain-script
|
|
|
|
|
script: build-cctools-port.sh
|
2017-04-17 02:34:24 +03:00
|
|
|
resources:
|
|
|
|
|
- 'taskcluster/scripts/misc/tooltool-download.sh'
|
2017-07-21 01:30:14 +03:00
|
|
|
toolchain-artifact: public/build/cctools.tar.xz
|
2017-07-20 11:56:49 +03:00
|
|
|
toolchains:
|
2017-08-15 03:39:48 +03:00
|
|
|
- linux64-clang-3.9
|
2017-01-30 21:12:57 +03:00
|
|
|
|
2017-04-28 18:12:31 +03:00
|
|
|
linux64-hfsplus:
|
2017-02-09 05:37:28 +03:00
|
|
|
description: "hfsplus toolchain build"
|
2017-01-30 21:12:57 +03:00
|
|
|
treeherder:
|
|
|
|
|
kind: build
|
Bug 1338061 - Move toolchain tasks to a separate "platform". r=dustin
The toolchain tasks are hard to spot on treeherder, in the ocean of
build and test jobs associated with the platforms they are currently
under.
Now that we have a significant number of toolchain tasks across
different platforms, it's even worse, especially combined with the fact
that they don't happen on every push.
To make them more easily visible, we move them to a new, separate,
"platform", with the name "toolchains", instead of having them in
different platforms. But since the distinction between Linux, OSX and
Windows 32/64 is still interesting to have, we create groups for each of
those platforms.
But because of bug 1215587, the jobs still end up associated to their
previous group, defeating the new grouping, so to work around that bug,
we also rename the jobs in subtle ways.
--HG--
extra : rebase_source : 6c093c070c18a64eba1c21bf2a2c97b2a9aaabc5
2017-01-27 05:46:22 +03:00
|
|
|
platform: toolchains/opt
|
|
|
|
|
symbol: TL(hfs+)
|
2017-01-30 21:12:57 +03:00
|
|
|
tier: 1
|
|
|
|
|
worker-type: aws-provisioner-v1/gecko-{level}-b-linux
|
|
|
|
|
worker:
|
|
|
|
|
docker-image: {in-tree: desktop-build}
|
|
|
|
|
max-run-time: 36000
|
2017-02-01 03:27:31 +03:00
|
|
|
run:
|
|
|
|
|
using: toolchain-script
|
|
|
|
|
script: build-hfsplus-linux.sh
|
|
|
|
|
resources:
|
Bug 1386588 - Avoid wildcards in toolchain resources lists. r=gps
Those resources are used to compute a unique identifier for the
toolchain, and changes to those files will change the unique identifier,
and lead to the toolchain being rebuilt.
Using wildcards, especially in the build-clang directory, makes all the
files from there used for the unique identifier, even files irrelevant.
The side effect is that any change to any json file for clang toolchains
currently triggers *all* clang toolchains to be rebuilt, which is a
waste of resources and time.
But while it is tempting to list all the files involved, it is also
tedious and error-prone. Specifically, listing the relevant patch files
for clang toolchain builds is bound to end up outdated. OTOH, we're not
trying to mitigate bad actors here, but just to avoid shooting ourselves
in the foot. And patch files are, in practice, not changed. The jsons
are changed to reference them or not, but the patches themselves don't
change in relevant ways. They may be updated for new versions of clang,
which require a json change anyways. So we ignore the patch files.
2017-08-02 11:42:40 +03:00
|
|
|
- 'build/unix/build-hfsplus/build-hfsplus.sh'
|
2017-04-15 03:03:05 +03:00
|
|
|
- 'taskcluster/scripts/misc/tooltool-download.sh'
|
2017-07-21 01:30:14 +03:00
|
|
|
toolchain-artifact: public/build/hfsplus-tools.tar.xz
|
2017-07-20 11:56:49 +03:00
|
|
|
toolchains:
|
2017-08-15 03:39:48 +03:00
|
|
|
- linux64-clang-3.9
|
2017-02-07 18:57:23 +03:00
|
|
|
|
2017-04-28 18:12:31 +03:00
|
|
|
linux64-libdmg:
|
2017-02-07 18:57:23 +03:00
|
|
|
description: "libdmg-hfsplus toolchain build"
|
|
|
|
|
treeherder:
|
|
|
|
|
kind: build
|
Bug 1338061 - Move toolchain tasks to a separate "platform". r=dustin
The toolchain tasks are hard to spot on treeherder, in the ocean of
build and test jobs associated with the platforms they are currently
under.
Now that we have a significant number of toolchain tasks across
different platforms, it's even worse, especially combined with the fact
that they don't happen on every push.
To make them more easily visible, we move them to a new, separate,
"platform", with the name "toolchains", instead of having them in
different platforms. But since the distinction between Linux, OSX and
Windows 32/64 is still interesting to have, we create groups for each of
those platforms.
But because of bug 1215587, the jobs still end up associated to their
previous group, defeating the new grouping, so to work around that bug,
we also rename the jobs in subtle ways.
--HG--
extra : rebase_source : 6c093c070c18a64eba1c21bf2a2c97b2a9aaabc5
2017-01-27 05:46:22 +03:00
|
|
|
platform: toolchains/opt
|
|
|
|
|
symbol: TL(libdmg-hfs+)
|
2017-02-07 18:57:23 +03:00
|
|
|
tier: 1
|
|
|
|
|
worker-type: aws-provisioner-v1/gecko-{level}-b-linux
|
|
|
|
|
worker:
|
|
|
|
|
docker-image: {in-tree: desktop-build}
|
|
|
|
|
max-run-time: 36000
|
2017-02-01 03:27:31 +03:00
|
|
|
run:
|
|
|
|
|
using: toolchain-script
|
|
|
|
|
script: build-libdmg-hfsplus.sh
|
2017-07-21 01:30:14 +03:00
|
|
|
toolchain-artifact: public/build/dmg.tar.xz
|
2017-07-14 05:07:40 +03:00
|
|
|
|
|
|
|
|
linux64-sccache:
|
|
|
|
|
description: "sccache toolchain build"
|
|
|
|
|
treeherder:
|
|
|
|
|
kind: build
|
|
|
|
|
platform: toolchains/opt
|
|
|
|
|
symbol: TL(sccache)
|
2017-07-26 09:17:15 +03:00
|
|
|
tier: 1
|
2017-07-14 05:07:40 +03:00
|
|
|
worker-type: aws-provisioner-v1/gecko-{level}-b-linux
|
|
|
|
|
worker:
|
|
|
|
|
docker-image: {in-tree: desktop-build}
|
|
|
|
|
max-run-time: 36000
|
|
|
|
|
env:
|
2017-08-02 14:06:10 +03:00
|
|
|
TOOLTOOL_MANIFEST: "browser/config/tooltool-manifests/linux64/releng.manifest"
|
2017-07-14 05:07:40 +03:00
|
|
|
run:
|
|
|
|
|
using: toolchain-script
|
|
|
|
|
script: build-sccache.sh
|
|
|
|
|
resources:
|
|
|
|
|
- 'taskcluster/scripts/misc/tooltool-download.sh'
|
|
|
|
|
toolchain-artifact: public/build/sccache2.tar.xz
|
2017-07-26 10:32:15 +03:00
|
|
|
toolchains:
|
2017-08-15 03:39:48 +03:00
|
|
|
- linux64-clang-3.9
|
