| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This executable in the workspace can be another Bazel binary whose
version will change with the code it's next to, or a shell script which
downloads a fixed version from some location.
RELNOTES: A tools/bazel script in the workspace will be executed
as an opportunity to use a fixed version of Bazel (not implemented for
the homebrew recipe yet).
Fixes #521
--
Change-Id: Id06177d9c2b259cd9d6fd62edb5abe541342dd05
Reviewed-on: https://bazel-review.googlesource.com/2620
MOS_MIGRATED_REVID=112477232
|
|
|
|
|
|
|
|
|
| |
Somewhat. The generated IntelliJ project is still somewhat broken and you need to manually exclude a few directories to use it and there is a mystical error about a missing method on truth.MapSubject, but at least now it fails in a less spectacular way.
Fixes #796.
--
MOS_MIGRATED_REVID=112458948
|
|
|
|
|
|
|
|
|
|
|
| |
With latest change to the bootstrap compilation, some options
were wrongly moved around.
Tested with `source scripts/ci/build.sh; bazel_build` for JAVA_VERSION
1.7 and 1.8.
--
MOS_MIGRATED_REVID=112409496
|
|
|
|
|
|
|
| |
This remove all C++ compilation in bootstrapping itself.
--
MOS_MIGRATED_REVID=112407516
|
|
|
|
|
|
|
| |
Another step towards no C++ compilation outside of Bazel for bootstrapping.
--
MOS_MIGRATED_REVID=112399835
|
|
|
|
|
|
|
|
| |
process-wrapper is a C++ tool, replacing by a dummy shell version to
reduce the number of C++ compiler calls during the bootstrap process.
--
MOS_MIGRATED_REVID=112398152
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112397181
|
|
|
|
|
|
|
| |
This method is used only once now so inline.
--
MOS_MIGRATED_REVID=112396086
|
|
|
|
|
|
|
|
| |
This simplify the bootstrap process and remove a C++ tool from
the bootstrap binary.
--
MOS_MIGRATED_REVID=112394555
|
|
|
|
|
|
|
|
|
| |
Instead use the current tools from the repository. This
simplifies the bootstrap binary and is a step towards
no C++ compilation for the bootstrap binary.
--
MOS_MIGRATED_REVID=112240524
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112239696
|
|
|
|
|
|
|
|
|
| |
Using java8-jdk will match both openjdk-8-jdk and oracle-java8-jdk similarly with java7-jdk. If
either of them are installed on the system allowing bazel to be installed in either case. Also the jdk source is not needed to create the bazel deb pacakge.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/785
MOS_MIGRATED_REVID=112132285
|
|
|
|
|
|
|
|
|
|
| |
0.1.3 was transformed into 0.1.~3 instead of 0.1.3
Tested the regexp manually with:
echo 0.1.3 | sed ...
echo 0.1.3rc3 | sed ...
--
MOS_MIGRATED_REVID=111884245
|
|
|
|
|
|
|
|
|
| |
The installer was missing the StdRedirect.dylib after a recent change.
This was breaking the Tutorial job on ci.bazel.io (and iOS builds using
that installer).
--
MOS_MIGRATED_REVID=111855462
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll-forward with fix
*** Original change description ***
Automated [] rollback of [].
*** Reason for rollback ***
Broke tests on Mac: https://google.com/url?sa=D&q=http%3A%2F%2Fci.bazel.io%2Fjob%2FBazel%2FJAVA_VERSION%3D1.8%2CPLATFORM_NAME%3Ddarwin-x86_64%2F269%2Fconsole
*** Original change description ***
Speed-up bootstrap on OS X by removing tool compilation.
--
MOS_MIGRATED_REVID=111833617
|
|
|
|
|
|
|
| |
For bazel on non-darwin architectures, this will simply be a stub, and should never be invoked. On darwin arcitectures, the tool will map xcode version to xcode path on the host system.
--
MOS_MIGRATED_REVID=111651147
|
|
|
|
|
|
|
| |
bazel server exits abruptly.
--
MOS_MIGRATED_REVID=111641619
|
|
|
|
|
|
|
| |
Fixes #752.
--
MOS_MIGRATED_REVID=111614541
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke tests on Mac: https://google.com/url?sa=D&q=http%3A%2F%2Fci.bazel.io%2Fjob%2FBazel%2FJAVA_VERSION%3D1.8%2CPLATFORM_NAME%3Ddarwin-x86_64%2F269%2Fconsole
*** Original change description ***
Speed-up bootstrap on OS X by removing tool compilation.
--
MOS_MIGRATED_REVID=110785493
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110704529
|
|
|
|
|
|
|
| |
will get rid of all the "ghost flakes" where tests crashed with no apparant reason printed into our logs. Now a stack trace is printed and an easy to understand failure reason, too.
--
MOS_MIGRATED_REVID=110142957
|
|
|
|
|
|
|
| |
This is useful because they have rules that depend on rules in the subpackages of examples and tools thus negating the benefit of not descending into them when running "bazel build //...".
--
MOS_MIGRATED_REVID=109774976
|
|
|
|
|
|
|
|
|
| |
This is a temporary hack until the base workspace goes away.
Fixes #652.
--
MOS_MIGRATED_REVID=109677574
|
|
|
|
|
|
|
|
|
| |
for debian package
Fixes #687
--
MOS_MIGRATED_REVID=109565904
|
|
|
|
|
|
|
| |
Manually tested with `source scripts/ci/build.sh; create_index_html rc2` where rc2 is the folder from 0.1.2rc2.
--
MOS_MIGRATED_REVID=108630774
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108500888
|
|
|
|
|
|
|
| |
annotation processor, and add its output directory to the source tree.
--
MOS_MIGRATED_REVID=108239745
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=108029812
|
|
|
|
|
|
|
| |
When output/bazel didn't exist (like in clean checkouts), "./compile.sh compile" would build a bazel without ijar, JavaBuilder_deploy.jar and their friends, which of course didn't work.
--
MOS_MIGRATED_REVID=107772112
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107377319
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was ending up installed as /bazel.
Also, the documented way of telling pkg_tar not to strip off the prefix
didn't work.
--
Change-Id: I593d17690526c614697369cab543aff1ba67de0a
Reviewed-on: https://bazel-review.googlesource.com/#/c/2222/
MOS_MIGRATED_REVID=107229260
|
|
|
|
|
|
|
| |
Bazel builds 4x faster than before, which also speeds up CI and running the test suite.
--
MOS_MIGRATED_REVID=107067655
|
|
|
|
|
|
|
|
|
| |
Avoid depending on extended regexp of gawk
--
Change-Id: I28a57c249c5b8078b410c365f51f400bcdc27997
Reviewed-on: https://bazel-review.googlesource.com/#/c/2240
MOS_MIGRATED_REVID=106877966
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|