| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
During bootstrap a number of tools are linked manually. These
link steps should take LDFLAGS to bootstrap bazel with custom
toolchain.
These tools are build-runfiles, process-wrapper and
namespace-sandbox.
cc_link() routine in compile.sh already takes LDFLAGS but not
the link steps for the tools listed above. They should all do so.
A developer can now do this to build Bazel:
CC="some-gcc" CXX="some-g++" LDFLAGS="-Lsome-glibc" \
JNI_LD_ARGS="-Lsome-glibc" ./compile.sh
--
Change-Id: Ifd1a03e989266a7fe3f1f92a7a44093b135fdc18
Reviewed-on: https://bazel-review.googlesource.com/2211
MOS_MIGRATED_REVID=106378256
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106307162
|
|
|
|
|
|
|
|
|
| |
back to getpwuid())
Also a minor compatibility fix in a sed invocation.
--
MOS_MIGRATED_REVID=106291639
|
|
|
|
|
|
|
|
|
|
|
| |
@bazel_tools repository.
The fix is to always compile tools when the Bazel binary is compiled and add the bootstrap arguments to bootstrap_test. This stil litters the git client with output files in random places, which is a bit difficult to fix, since //src:bazel expects these files to be there so that it can embed them into the output binary.
I didn't notice this issue because tools/jdk/*_deploy.jar is in the .gitignore file, thus, when "git status" reported nothing, I asumed I ran the build in a clean client.
--
MOS_MIGRATED_REVID=105206124
|
|
|
|
|
|
|
|
| |
Fixes the illegal option error here:
http://ci.bazel.io/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=darwin-x86_64/162/console
--
MOS_MIGRATED_REVID=105189685
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105060098
|
|
|
|
|
|
|
|
|
|
|
| |
This refactor a bit the docker rules to reuse the tarball construction.
Also introduce the debian archive for the release process.
RELNOTES[NEW]: Debian and tar packaging is now supported
(see tools/build_defs/pkg/README.md).
--
MOS_MIGRATED_REVID=105053604
|
|
|
|
|
|
|
|
| |
With that change, all the git hash will have the same length in
the release notes, even when specifying the full commit hash.
--
MOS_MIGRATED_REVID=104861463
|
|
|
|
|
|
|
|
|
|
|
| |
* -n: Create a new network namespace with only loopback interface.
* -r: set the uid/gid inside the sandbox to be root (instead of nobody)
so that setuid programs like ping can still run when needed.
--
Change-Id: I8ab434e47e0f6933ee9de02e135c8daec39fe73f
Reviewed-on: https://bazel-review.googlesource.com/#/c/2101/
MOS_MIGRATED_REVID=104858163
|
|
|
|
|
|
|
|
|
| |
So this can be run in a git clone that has commit hooks
(e.g., for adding Gerrit change id) without adding garbage
to the commit log.
--
MOS_MIGRATED_REVID=104761737
|
|
|
|
|
|
|
| |
This is currently unused deadweight, but will be used pretty soon to access the tools directory instead the menagerie of various odd mechanism we currently use.
--
MOS_MIGRATED_REVID=104737151
|
|
|
|
|
|
|
|
|
|
|
| |
Before, CI was exiting when an exit code of 0 was returned, failing
to build the installer script.
Tested with `bash -c 'source scripts/ci/build.sh; bazel_build output/ci'`
and checking output/ci for the installer.
--
MOS_MIGRATED_REVID=104647177
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104510412
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104506836
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Prevent test from JavaBuilder to be run (mark them as JDK8 only).
- Hack to replace the JavaBuilder target so that test that needs JavaBuilder
will depends on the pre-built binary version.
Tested: bash -c 'export JAVA_VERSION=1.7; source scripts/ci/build.sh; bazel_build'
(and verified that there is no build failure). We might still have failing
tests (worker and runfiles) but the failure seems like flakiness.
--
MOS_MIGRATED_REVID=104504123
|
|
|
|
|
|
|
|
|
|
|
| |
Instead set a BUILD_UNSTABLE=1 environment variable such
as a subsequent change to Jenkins can mark our build as
unstable instead of failed when we have test flakiness.
This would also allow to test the Tutorial with flaky builds.
--
MOS_MIGRATED_REVID=104501213
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Follow redirects when downloading files:
The github provided file lies after several redirect, giving a bad jars
(see http://ci.bazel.io/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=linux-x86_64/144/console).
- Remove building tools as part of the determinism tests:
With recent update, JavaBuilder can no longer be built with Java 7,
so we use a pre-built binary from version 0.1.0. However, the
determinism test was still using it as a point of comparison. Removing
tools from the determinism test prevent building JavaBuilder without
giving up on testing actual determinism (building Bazel already contains
all the edge-cases).
Tested with `bash -c 'export JAVA_VERSION=1.7; source scripts/ci/build.sh; bazel_build'`
--
MOS_MIGRATED_REVID=104480161
|
|
|
|
|
|
|
|
|
| |
The latest update of javac broke JDK 7 because we were using a JavaBuilder
that is not synced with the javac. Fix it by using javac from our 0.1.0
release.
--
MOS_MIGRATED_REVID=104431158
|
|
|
|
|
|
|
|
|
|
|
| |
The headers were modified with
`find . -type f -exec 'sed' '-Ei' 's|Copyright 201([45]) Google|Copyright 201\1 The Bazel Authors|' '{}' ';'`
And manual edit for not Google owned copyright. Because of the nature of ijar, I did not modified the header of file owned by Alan Donovan.
The list of authors were extracted from the git log. It is missing older Google contributors that can be added on-demand.
--
MOS_MIGRATED_REVID=103938715
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=103736505
|
|
|
|
|
|
|
| |
This is breaking our CI system. Also removed the UTF-8 quotes.
--
MOS_MIGRATED_REVID=103534994
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change deprecate JDK 7 as JavaBuilder follow changes in Java 9
and might use Java 8 features. We will maintain a build with the
JDK 7 as long as possible but this build won't include updates
in JavaBuilder.
RELNOTES[INC]: Bazel requires JDK 8 to run.
--
MOS_MIGRATED_REVID=103069207
|
|
|
|
|
|
|
|
| |
This a first step toward supporting platform that does not requires
to generate released artifacts.
--
MOS_MIGRATED_REVID=102999025
|
|
|
|
|
|
|
| |
Fixes #440
--
MOS_MIGRATED_REVID=102739492
|
|
|
|
|
|
|
|
|
|
|
| |
github-release actually takes a glob, not a list of file and tmpdir
was not global so because errexit was set it leads to the job failing.
Tested by simulating a release environment on my machine but we cannot
fully test it until the next release.
--
MOS_MIGRATED_REVID=102642172
|
|
|
|
| |
MOS_MIGRATED_REVID=102637361
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102567966
|
|
|
|
|
|
|
|
|
| |
android_{ndk,sdk}_repository rules themselves.
This is to that the Android tests also work on OS X (otherwise, we'd end up creating a file called "BUILD" in its root, which doesn't work, because it already has a directory called "build")
--
MOS_MIGRATED_REVID=102484286
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102343488
|
|
|
|
|
|
|
|
| |
This will make the user experience a bit nicer as it should make
the first run of bazel faster.
--
MOS_MIGRATED_REVID=102338873
|
|
|
|
|
|
|
| |
How comes this is ok on linux???
--
MOS_MIGRATED_REVID=102338200
|
|
|
|
|
|
|
| |
Without those check, a wrong call can wipe unwanted stuff
--
MOS_MIGRATED_REVID=102337203
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this script, the easiest way to run the test suite is now:
bash -c "export ANDROID_SDK_PATH=$HOME/bin/android-sdk-linux; \
export ANDROID_NDK_PATH=$HOME/bin/android-ndk-r10e; \
source ./scripts/ci/build.sh; \
bazel_build output/ci"
--
MOS_MIGRATED_REVID=102334239
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102124504
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102022958
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101960679
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101929112
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=101926016
|
|
|
|
|
|
|
|
| |
This file is a dummy and cannot be extracted from the Bazel workspace
so create it.
--
MOS_MIGRATED_REVID=101925956
|
|
|
|
|
|
|
|
|
|
| |
fmt behaves totally differently depending on the version and on the
OS, use fold instead that has a consistent behaviour accross platform.
Tested with bazel test //scripts/release/... on OSX and Linux.
--
MOS_MIGRATED_REVID=101567574
|
|
|
|
|
|
|
| |
--
Change-Id: I4e65cc583e758d2f7e45209ffcb37f6a871e2ed7
Reviewed-on: https://bazel-review.git.corp.google.com/#/c/1840
MOS_MIGRATED_REVID=101462155
|
|
|
|
|
|
|
|
|
|
|
|
| |
use non-declared inputs) and safety (spawns can no longer affect the host system, e.g. accidentally wipe your home directory). This implementation works on Linux only and uses Linux containers ("namespaces").
The strategy works with all actions that Bazel supports (C++ / Java compilation, genrules, test execution, Skylark-based rules, ...) and in tests, Bazel could successfully bootstrap itself and pass the whole test suite using sandboxed execution.
This is not the default behavior yet, but can be activated explicitly by using:
bazel build --genrule_strategy=sandboxed --spawn_strategy=sandboxed //my:stuff
--
MOS_MIGRATED_REVID=101457297
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that Bazel finds Android tools and update the tools themselves to handle their new location.
This paves the way for eventually referencing every tool this way.
We have to figure out if android_http_tools_repository is the right way to distribute the Android tools, but now that we don't have a binary distribution yet, it's not an immediate problem.
This will break existing users of Android support in Bazel, whom I'll inform over bazel-discuss.
Fixes #384.
--
MOS_MIGRATED_REVID=101456190
|
|
|
|
|
|
|
| |
It rotted somewhere along the way and tried to build Objective C tools on Linux, and unsurprisingly, failing.
--
MOS_MIGRATED_REVID=101445358
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=100915378
|
|
|
|
|
|
|
|
| |
Moving it to scripts/ci let that unchanged and that results in an error
in the CI system.
--
MOS_MIGRATED_REVID=100825881
|
|
|
|
|
|
|
| |
--
Change-Id: I424db210611f94b986eda872626a97415221fcea
Reviewed-on: https://bazel-review.googlesource.com/1800
MOS_MIGRATED_REVID=100806076
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It provides method to build, package and deploy artifacts, as
well as constructing announcement mails:
- bazel_build build bazel with the good label, execute the tests,
build the packages and copy the artifacts into a release directory.
- bazel_release deploy the relase to GCS and Github and send an
announcement mail.
--
Change-Id: I68f5a600c0718fac5fa12423d1cb8e0cc86728b5
Reviewed-on: https://bazel-review.googlesource.com/#/c/1811
MOS_MIGRATED_REVID=100805636
|
|
|
|
|
|
|
| |
--
Change-Id: Ia70ca1b8482e10bc1ac91799aa238f8613e5c824
Reviewed-on: https://bazel-review.googlesource.com/#/c/1801
MOS_MIGRATED_REVID=100476467
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
exec(3) under mingw converts every command line argument that looks like Unix path
into Windows path when executing non-mingw images (criteria for non-mingw image is
that the image does not depend on msys-<version>.dll). This affects bazel labels
(`//foo:bar` becomes `/foo:bar` for example).
This CL:
1) Replaces usage of execv(3) with Windows-native CreateProcess.
2) Converts all command line arguments that are indeed paths into Windows paths.
--
MOS_MIGRATED_REVID=100386350
|