| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We'll just replace them with either native support for running tests inside
Docker containers on CI or with VMs running the operating system.
This gets rid of the "let's download 8 GB of Docker images" step when running
`bazel build //...`.
RELNOTES: None.
Closes #4506.
PiperOrigin-RevId: 183078052
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel-toolchains/releases/tag/f3b0970
PiperOrigin-RevId: 182058527
|
|
|
|
|
|
| |
https://github.com/bazelbuild/bazel-toolchains/releases/tag/b49ba36
PiperOrigin-RevId: 178294425
|
|
|
|
|
|
|
|
|
| |
The latest version of re2 contains fixes that makes it compatible with new changes in Bazel.
Fixes #4233
RELNOTES: None.
PiperOrigin-RevId: 178087275
|
|
|
|
|
|
| |
Fixes #2355.
PiperOrigin-RevId: 174871644
|
|
|
|
| |
PiperOrigin-RevId: 173304095
|
|
|
|
|
|
|
| |
now routed through https, so those http requests currently cause a redirect. This removes the redirect.)
RELNOTES: Update "mirror.bazel.build" urls to use https.
PiperOrigin-RevId: 173175888
|
|
|
|
|
|
|
|
| |
method desugaring for Android.
RELNOTES: none
PiperOrigin-RevId: 171891682
|
|
|
|
| |
PiperOrigin-RevId: 171048721
|
|
|
|
| |
PiperOrigin-RevId: 167720760
|
|
|
|
|
| |
Change-Id: I3648aadad5895f80051ada39d0ca862dd437cc58
PiperOrigin-RevId: 167266028
|
|
|
|
|
| |
Change-Id: I08323cfb98b6d52017bc1285d9d63370a20378eb
PiperOrigin-RevId: 167259969
|
|
|
|
|
|
|
|
|
|
| |
For any errors that are due to failures in the remote caching /
execution layers Bazel now returns exit code 34 (ExitCode.REMOTE_ERROR).
This includes errors where the remote cache / executor is unreachable or
crashes. It does not include errors if the test / build failure is due
to user errors i.e. compilation or test failures.
PiperOrigin-RevId: 167259236
|
|
|
|
| |
Change-Id: I3648aadad5895f80051ada39d0ca862dd437cc58
|
|
|
|
|
|
|
|
| |
WORKSPACE file, removing j2objc.WORKSPACE.
Updates J2ObjC version to 2.0.3, which has its own BUILD file.
RELNOTES: J2ObjC version updated to 2.0.3.
PiperOrigin-RevId: 167135399
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
./compile.sh srcs has been broken at several time because this
test cannot run on our internal presubmit (more precisely, don't see
most breakage on our internal presubmit). Making this test a Bazel
test should fix that at the same time reducing the scope of ./compile.sh
(with the other move of the determinism test, this make compile.sh
being only the bootstrapping script).
To do so, we fetch the list of sources in the repository through
a skylark repository and use genquery to interrogate the list of
sources in //:srcs filegroup.
Change-Id: If83af28a366cc0c52a7327ce9ed2489c7e88532f
PiperOrigin-RevId: 166064682
|
|
|
|
|
|
|
|
|
|
|
| |
Send the startup options tagged with their origin so that the server has correct information about the command line as the client received it.
Removes the unconditional stderr printing of all bazelrc startup options in the bazel client. Instead, the startup options are sent to the server and the same informational printing is gated on the --announce_rc option. This avoids unconditional log spam to stderr early in startup. If the server is unreachable or there are errors parsing startup options, the message is still printed to stderr.
Fixes https://github.com/bazelbuild/bazel/issues/2530.
RELNOTES: --announce_rc now controls whether bazelrc startup options are printed to stderr.
PiperOrigin-RevId: 165211007
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Rollforward with fix
*** Original change description ***
Automated rollback of commit e5f970906594d9097bb7c3736b2de1750cc8655f.
*** Reason for rollback ***
Break apple test on darwin.
*** Original change description ***
Refactor docker tests to be buildable without docker.
This make this build a bit non-deterministic since the way
it will be built depend on wether docker is installed or not.
We now use the docker_pull from bazelbuild/continuous-integration
to generate the base docker images and generate a fake docker binary
that j...
***
PiperOrigin-RevId: 162731090
|
|
|
|
| |
PiperOrigin-RevId: 162601644
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Break apple test on darwin.
*** Original change description ***
Refactor docker tests to be buildable without docker.
This make this build a bit non-deterministic since the way
it will be built depend on wether docker is installed or not.
We now use the docker_pull from bazelbuild/continuous-integration
to generate the base docker images and generate a fake docker binary
that just error out when docker is not found so test will fails.
Note that the docker_pull is set to timeout after an hour and
can be extremely slow...
***
PiperOrigin-RevId: 162598046
|
|
|
|
| |
PiperOrigin-RevId: 162532778
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This make this build a bit non-deterministic since the way
it will be built depend on wether docker is installed or not.
We now use the docker_pull from bazelbuild/continuous-integration
to generate the base docker images and generate a fake docker binary
that just error out when docker is not found so test will fails.
Note that the docker_pull is set to timeout after an hour and
can be extremely slow so we also set it to non quiet.
Fixes #3278.
Change-Id: I98d5b436e424f53981e113c1a4fd1346a5564df7
PiperOrigin-RevId: 162476033
|
|
|
|
| |
PiperOrigin-RevId: 161850684
|
|
|
|
| |
PiperOrigin-RevId: 161693427
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a better location and tools/cpp is packaged in embedded_tools that make the test ends-up in embedded_tools, which is requiring network access
to build embedded_tools!
Side-effect: have to correctly mock the bazel workspace file on a couple
of tests.
This is blocking on https://bazel-review.googlesource.com/c/12350/
PiperOrigin-RevId: 160265524
|
|
|
|
|
| |
Change-Id: I2c588a4e965f4f0f15db8d447c63307b1baf1cd0
PiperOrigin-RevId: 157462273
|
|
|
|
|
|
|
|
| |
A mirror and source code are provided at the usual location:
http://mirror.bazel.build/openjdk/index.html
Change-Id: I081df934c2bda7e9cc03246dfbdeca75404acc97
PiperOrigin-RevId: 156302005
|
|
|
|
| |
PiperOrigin-RevId: 155511878
|
|
|
|
|
| |
Change-Id: I32f6b16955ecefc242af8d9261418452d698c9ff
PiperOrigin-RevId: 154812955
|
|
|
|
|
|
|
| |
This reverts commit 5235d06159ba6fee412bee261ea7867d061252b0.
Unfortunately, we noticed several build errors / test failures internally due this
change.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially
the development version of protobuf 3.2.0 and windows specific fixes
from laszlo. Those fixes will be merged into protobuf soon:
https://github.com/google/protobuf/pull/2969).
For instructions on how to update protobuf for bazel see
README.bazel.md.
Change-Id: Ic1daafe30270cb6bcc6231e6c94fb670af0475e7
|
|
|
|
| |
This reverts commit ea82aa115794b019472b44d4f94ed902c1217f30.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update protobuf to @laszlocsomor's fork of protobuf. This is essentially
the development version of protobuf 3.2.0 and windows specific fixes
from laszlo. Those fixes will be merged into protobuf soon:
https://github.com/google/protobuf/pull/2969).
For instructions on how to update protobuf for bazel see
README.bazel.md.
Change-Id: I4f663955b0baeea3232b69ce32d9292427f5274a
|
|
|
|
|
|
|
|
|
|
|
|
| |
As of Bazel 0.4.5, the android_sdk_for_test and android_ndk_for_test are bound in android.WORKSPACE, so we do not need to include them in the main Bazel WORKSPACE file. I've update the comments to reflect that all that is needed to run the tests is android_sdk_repository and android_ndk_repository and the environment variables that they read.
Also, delete scripts/workspace_user.sh. All of its functionality (reading environment variables, detecting api levels, build tools versions) is now part of android_{s,n}dk_repository.
Fixes https://github.com/bazelbuild/bazel/issues/2284.
--
PiperOrigin-RevId: 151032551
MOS_MIGRATED_REVID=151032551
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We're using Azul Systems, Inc.'s Zulu® OpenJDK build[1], as it's a good
vanilla build of OpenJDK available for our three most important
platforms:
zulu8.20.0.5-jdk8.0.121-linux_x64.tar.gz
zulu8.20.0.5-jdk8.0.121-macosx_x64.zip
zulu8.20.0.5-jdk8.0.121-win_x64.zip
You can build & run a Bazel binary with an embedded JDK by simple doing:
bazel build //src:bazel_with_jdk
bazel-bin/src/bazel_with_jdk info
The "bazel license" command prints the license of the embedded OpenJDK.
We mirror the binaries and sources of the OpenJDK used for bundling on
this website:
https://bazel-mirror.storage.googleapis.com/openjdk/index.html
RELNOTES: Bazel can now be built with a bundled version of the OpenJDK.
This makes it possible to use Bazel on systems without a JDK, or where
the installed JDK is too old.
[1] http://www.azul.com/downloads/zulu/
--
PiperOrigin-RevId: 150440467
MOS_MIGRATED_REVID=150440467
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 2346f5a01561f695a2b2ba7655359d5020105077.
It breaks bazel build in freebsd[1]. The solution is to patch
https://svnweb.freebsd.org/ports/head/devel/protobuf/files/. I
rolled-back this since the other builds will not automatically start if
Bazel is broken.
[1] http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=freebsd-11/1312/
Change-Id: I7e939a4293d799ab6dd67f93d219d1efdf4cd901
|
|
|
|
|
|
|
| |
with some backports from HEAD
(:java_toolchain, internal_gen_well_known_protos_java)
Change-Id: I54be8809f411ec8cb02203b478f699e1fccb5f62
|
|
|
|
|
|
|
|
| |
This allows proto_library to be used out of the box by adding a repository entry that points to the protobuf distro in one's WORKSPACE file.
--
PiperOrigin-RevId: 147808147
MOS_MIGRATED_REVID=147808147
|
|
|
|
|
|
|
|
| |
These are not used anymore.
--
PiperOrigin-RevId: 146381129
MOS_MIGRATED_REVID=146381129
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Does not build: http://ci.bazel.io/job/Bazel/1129/
*** Original change description ***
Export dot-format graphs as-is and download dot as an external repo
--
PiperOrigin-RevId: 142748151
MOS_MIGRATED_REVID=142748151
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 142692462
MOS_MIGRATED_REVID=142692462
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks CI
"Parameter 'url' has no default value", see http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.7,PLATFORM_NAME=linux-x86_64/1104/console.
*** Original change description ***
Make Bazel build dot
This change has several parts, it:
* Adds a "make" repository rule, which runs ./configure && make on a
repository.
* Modifies the tar.gz decompressor to restore timestamps. This was
an issue with dot, as make examines the timestamp to determine if
files need to be rebuilt. Because Bazel was not preserving the
archive's timestamp, it was rebuilding things that it did not need to
(and, I think, exposed some bugs in dot's Makefile).
* Actually add dot as an externa...
***
--
PiperOrigin-RevId: 142469299
MOS_MIGRATED_REVID=142469299
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change has several parts, it:
* Adds a "make" repository rule, which runs ./configure && make on a
repository.
* Modifies the tar.gz decompressor to restore timestamps. This was
an issue with dot, as make examines the timestamp to determine if
files need to be rebuilt. Because Bazel was not preserving the
archive's timestamp, it was rebuilding things that it did not need to
(and, I think, exposed some bugs in dot's Makefile).
* Actually add dot as an external repository. I made the dot-graph
target manual, so it won't be downloaded/built by the default //...
target.
* Remove dot scrubbing from the Bazel export process.
* Added some names to download_and_extract params, because it's really
annoying to only be able to reference them positionally.
--
PiperOrigin-RevId: 142452055
MOS_MIGRATED_REVID=142452055
|
|
|
|
|
|
|
|
|
| |
java_xxx_proto_library rules now look for toolchains in the external repo @com_google_protobuf_xxx//:xxx_toolchain
This still requires getting protobuf's GitHub repository to build with Bazel.
--
MOS_MIGRATED_REVID=140420903
|
|
|
|
|
|
|
|
|
|
|
| |
test_maven_aar_skylark is essentially an android_integration_test and as such
requires that android_sdk_for_testing and android_ndk_for_testing be properly
set up.
See https://github.com/bazelbuild/bazel/issues/2086
--
MOS_MIGRATED_REVID=139384309
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Use proto_lang_toolchain() in java_proto_library, after fixing breakage.
Verified on Jenkins, http://ci.bazel.io/job/Gerrit-bazel-tests/169/
*** Original change description ***
Automated [] rollback of commit a396b070ae36032a973672e11145533621c39edc.
*** Reason for rollback ***
Breaks tests on latest, as proto_lang_toolchain didn't make it into the 0.4.0 release
see http://ci.bazel.io/job/bazel-tests/306/BAZEL_VERSION=latest,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Use proto_lang_toolchain() in java_proto_library.
--
MOS_MIGRATED_REVID=138432193
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks tests on latest, as proto_lang_toolchain didn't make it into the 0.4.0 release
see http://ci.bazel.io/job/bazel-tests/306/BAZEL_VERSION=latest,PLATFORM_NAME=linux-x86_64/console
*** Original change description ***
Use proto_lang_toolchain() in java_proto_library.
--
MOS_MIGRATED_REVID=138372522
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=138161512
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
**Experimental**
This is an initial implementation of the maven_jar rule in Skylark, targeted at
the FRs in issue #1410.
Implemented a wrapper around the maven binary to pull dependencies from
remote repositories into a directory under {output_base}/external.
Attributes `name`, `artifact`, `repository`, `sha1` have been implemented,
but not `server`.
Caveat: this rule assumes that the Maven dependency is installed in the
system. Hence, the maven_skylark_test integration tests are tagged with
"manual" and commented out because the Bazel CI isn't configured with
the Maven binary yet.
Added a serve_not_found helper for 404 response tests.
Usage:
```
load("@bazel_tools//tools/build_defs/repo:maven_rules.bzl", "maven_jar")
maven_jar(
name = "com_google_guava_guava",
artifact = "com.google.guava:guava:18.0",
sha1 = "cce0823396aa693798f8882e64213b1772032b09",
repository = "http://uk.maven.org/maven2",
)
```
With regards to server, there are some limitations with retrieving a
maven_server's attribute at Loading Phase without the use of hacky macros
(issue #1704), and even if macros are used, the maven_server is not treated as
an actual dependency by maven_jar. There is a test (`test_unimplemented_server_attr`)
to ensure that the error message to shown to users if they use the server
attribute with this rule.
--
Change-Id: I167f9d13835c30be971928b4cc60167a8e396893
Reviewed-on: https://bazel-review.googlesource.com/c/5770
MOS_MIGRATED_REVID=133971809
|
|
|
|
|
|
|
|
|
|
|
| |
bfaff29b1bafd7892a2197b7cf826e1be0ff3927.
Without the newline, our bazel/scripts/ci/build.sh will append an android_sdk_repository() rule into the file in such a way, that it produces a syntax error.
Also fix the build.sh script to be more resilient and not actually require the newline.
--
MOS_MIGRATED_REVID=130737331
|