Age | Commit message (Collapse) | Author |
|
push_binary_dir should be the single source of truth for the PUSHDIR,
so push_scp_url should not add any prefixes. If we wish to have
a public_html in the path, we should add it in push_binary_url instead,
since that is what we use to create the push directory in
tcwg-build-llvm.sh. But for now I don't think we need public_html at all
anymore.
Change-Id: Ie26430fbf00f94ffd1c70365c95a251fb14ce46c
|
|
dev-01 is having hardware issues, so we can't rely on it anymore. Try
uploading binaries to bkp-01 instead.
Change-Id: I8aca250b4d20a6b1c1bfe4ab7575e8699560cee5
|
|
Fixes for:
https://github.com/koalaman/shellcheck/wiki/SC2207
Are using the bash 4.x 'mapfile' syntax where the
input to the array is seperated by newlines.
If it's separated by spaces we use 'read' instead.
Support for selecting libc in MakeRelease.job was
removed in 3fa23da28ad73d0fe4b512c4aab269b5280a6650.
So remove references to "libc" which were expanding
to nothing anyway.
In tcwg-llvm-common.sh PROJECTS->BRANCHED_PROJECTS
is not strictly needed. However shellcheck can't
tell that the local PROJECTS in this file is
different from the PROJECTS in tcwg-llvm-build.sh.
Change-Id: Ie55968e3bf185d0bd5795fe48014636cda1009bc
|
|
(all error/style level warnings)
SC1035: missing whitespace
SC2068: double quote array expansions
SC2145: argument mixes string and array
SC1066: Don't use $ on the left side of assignments
SC2126: Use grep -c instead of grep|wc
Change-Id: Ia53070d3e2c9aea9f626fdb7b2b5bfc9e1f8e682
|
|
Change-Id: I702798bb1ec289def11ea8d9d3156834e4e4bf9a
|
|
Change-Id: Iec34423be746d6267342068037e88e287374ab58
|
|
As discussed in TCWG-1134, we need a list of projects to checkout if the
branch is master and there is a revision (buildbot and pre-commit base
cases) as well as a branch and no list (for pre-commit patch cases.
The relationship between lists and branches is that having a branch and
not being in the list is ok, but being in the list and not having a
branch is not. This patch addresses that, so that we can create any
number of trigger jobs without worrying about the parameters we pass.
It should either be safe, user error, or the job will bail.
Needs https://review.linaro.org/19777 to work.
Change-Id: I83fa889f3d3ebf80f08ffed218d4e72e40a88ecc
|
|
This implements the simplest way to do a pre-commit test as described in
TCWG-1124: Any tree that needs building will push to the appropriate
branch all the projects that they need, regardless of changes.
This can only work if the underlying process guarantees that:
1. No user will ever create a repo with that name, even by accident,
for example, by Forcing an exclusive namespace like
jenkins-test/username/branch.
2. The branches are deleted at the end, regardless of success or failure.
To re-start a build on the same branch, just push it again and re-run the
job. This may not be possible for Jenkins to do (as it doesn't have
write permissions to all git repos we could possibly try to build from),
so this will need some coordination with the rest of the LLVM scripts.
This change also re-factors how to checkout the llvm repositories, so
that we can control on a branch level and collect only the relevant SVN
revisions from the branches we have actually checked out.
Change-Id: I2f77ac49f23ce79f2057f1cc90e1ccd63e2a45f4
|
|
In addition to an external toolchain, we also want to control which
system compiler is to be used. If an option is passed, that will be the
set into CC/CXX and used by the scripts in the same way an external
toolchain would.
Change-Id: I25366c6c3c725ead1667d7b8828b1100e5e925d3
|
|
Change-Id: I34c1f574dca80eee02f10c140a3cfc7d5db5f018
|
|
Change-Id: I339921b036f92b8515fdafdb891e3d59e14bdf70
|
|
checkout problem
Change-Id: I0d4bd207c9f278539e7be48e86b3047a1f012242
|
|
Change-Id: I419b36b027a4d979d5152274a0095bbe4596d4a9
|
|
To make sure stage two builds the same revision as stage 1 and to
correctly identify the SVN revision of an LLVM build, calculate the SVN
revision if one it not provided.
Always passing down toolchain and revision, as they should always be
available at that point. The test-suite job is free to ignore it.
Change-Id: I5a79284ac4fbc5a42e5d85e69f39a8c6d68e0cc6
|
|
Change-Id: I422ce0666089864ab50bf065af171c7ff0e4d1dd
|
|
Fixing this warning means that errors from the push_binary_*
functions won't be silently ignored.
$ shellcheck tcwg-llvm-common.sh
In tcwg-llvm-common.sh line 93:
local PUSHDIR="$(push_binary_dir "$TYPE")"
^-- SC2155: Declare and assign separately to avoid masking return values.
In tcwg-llvm-common.sh line 101:
local BINARY="$(push_binary_name "$TAG" "$TRIPLE")"
^-- SC2155: Declare and assign separately to avoid masking return values.
In tcwg-llvm-common.sh line 102:
local PUSHDIR="$(push_binary_dir "$TYPE")"
^-- SC2155: Declare and assign separately to avoid masking return values.
Change-Id: I075e9490ea10ca857bb6dda13274d862048f4251
|
|
Change-Id: I416464abd1b1d62b5e9425b97b7e4649ad14d156
|
|
This is an NFC patch that just common things up. I'm making sure that we
only handle URLs and toolchain downloads in a single place, which will
later be very useful when we get Jenkins to ask these scripts to create
the trigger files.
This is the first part of TCWG-1117. Adding the trigger files will be
the second.
I have tested on my box by sourcing the common file and calling the
functions with the right parameters as well as running the scripts
(build/release/test) with the appropriate arguments but with the core
logic actually commented out.
I have some empty tar balls with the right names on dev-01. :)
Change-Id: Ice435ad9d5e20152e295413075c32a396ffc5e2a
|