| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
Closes #5679.
PiperOrigin-RevId: 208194222
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old list was, in order:
- %workspace%/tools/bazel.rc (unless --nomaster_bazelrc)
- %binary_dir%/bazel.bazelrc (unless --nomaster_bazelrc)
- system rc, /etc/bazel.bazelrc or in %ProgramData% for Windows (unless --nomaster_bazelrc)
- the first of the following gets called the "user" bazelrc
- path passed by flag --bazelrc
- %workspace%/.bazelrc
- $HOME/.bazelrc
The new list is hopefully a bit more consistent, as:
- system rc (unless --nosystem_rc)
- workspace, %workspace%/.bazelrc (unless --noworkspace_rc)
- user, $HOME/.bazelrc (unless --nohome_rc)
- command-line provided, passed as --bazelrc or nothing if the flag is absent.
This list removes two less than useful locations, duplication in the Workspace directory, and the rc next to the bazel binary. This location made sense at Google but is generally nonsensical elsewhere so we are removing it. It also stops the user local rc file from being overriden by passing in a custom file in --bazelrc.
In both old and new, --ignore_all_rc_files disables all of the above.
For a transition period, any file that you would have loaded but was not read will cause a WARNING to be printed. If you want the old file to still be read without moving its location, you can always import it into one of the new standard locations, or create a symlink.
Closes #4502, except for cleanup to remove the warning after a transition period of 1 Bazel version has passed.
RELNOTES[INC]: New bazelrc file list.
PiperOrigin-RevId: 207189212
|
|
|
|
|
|
|
|
|
|
| |
to avoid confusion between the LHS and RHS host_javabases.
The LHS --host_javabase option should be considered deprecated and will
eventually be removed.
RELNOTES: Rename the startup flag --host_javabase to --server_javabase to avoid confusion with the build flag --host_javabase
PiperOrigin-RevId: 206015757
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 205975626
|
|
|
|
|
|
|
| |
Fixes #5529
Change-Id: Ie3d45c4882355bd2f8b02c5afa1ad0248f28d505
PiperOrigin-RevId: 203751587
|
|
|
|
|
|
|
|
|
|
|
| |
Use the "with" statement to open files in various
Python scripts used by Bazel, to ensure these
files are closed eagerly.
See https://github.com/bazelbuild/bazel/issues/5512
RELNOTES: none
PiperOrigin-RevId: 203346678
|
|
|
|
|
|
| |
Closes #5486.
PiperOrigin-RevId: 202634385
|
|
|
|
|
|
|
|
| |
Based on work of Sun Zhiyi <zhiyisun@gmail.com>.
Closes #5360.
PiperOrigin-RevId: 201339882
|
|
|
|
|
|
| |
Closes #5403.
PiperOrigin-RevId: 201007405
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a flag to the installer to skip uncompressing the base image during installation.
Uncompressing the base image during installation can be problematic:
1. If you configure the startup option `output_user_root` you'll wind up extracting the image twice. Once during installation and a second time during the first bazel invocation in your project.
2. If you're bootstrapping Bazel in a controlled environment (in my case via Nix) then you can get permission errors if Bazel defaults to extracting to the home directory. There's no way to skip this extraction and for the time being I have resorted to seting `HOME` to a throw away directory during install.
Closes #5303.
PiperOrigin-RevId: 201004235
|
|
|
|
|
|
|
|
| |
with empty default value to keep the script behavior unchanged. javac is not given a large enough max heap on Raspberry Pi 3. This change but allows the user to override the setting.
RELNOTES:
The BAZEL_JAVAC_OPTS environment variable allows arguments, e.g., "-J-Xmx2g", may be passed to the javac compiler during bootstrap build. This is helpful if your system chooses too small of a max heap size for the Java compiler during the bootstrap build.
PiperOrigin-RevId: 200557606
|
|
|
|
|
|
|
|
|
|
|
| |
- Updates the embedded JDK to Azul Zulu 9.0.7
- All integration tests use Bazel with the embedded JDK
Also updated: http://storage.googleapis.com/bazel-mirror/openjdk/index.html
Closes #5312, #5314, #5315
PiperOrigin-RevId: 200055008
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The option --experimental_distdir has been introduced 4 months
ago and was completely unproblematic ever since. Moreover, it
is now used productively, both in our own bootstrapping process[1],
as well as in external packaging of projects using bazel[2]. So
make this option non-experimental. We still keep the old name as
an alternative to not break existing uses.
Related: #5175.
RELNOTES: The --distdir option is no longer experimental. This
option allows to specify additional directories to look for
files before trying to fetch them from the network. Files from
any of the distdirs are only used if a checksum for the file
is specified and both, the filename and the checksum, match.
[1] Commit 3c9cd82b847f3ece8ec04b2029bd5e8ad0eb7502
[2] https://github.com/gentoo/gentoo/blob/7379cdb578b0c070c846c3fa9f71470e2c5d1320/sci-libs/tensorflow/tensorflow-1.8.0-r1.ebuild#L168
Change-Id: I536238f9bdbad6b4f7222b4f6a1464d70d9f3be3
PiperOrigin-RevId: 199637265
|
|
|
|
|
|
|
|
|
| |
This use of seq is easy enough to emulate in bash which is a declared
bootstrap dependency.
Closes #5321.
PiperOrigin-RevId: 199248546
|
|
|
|
|
|
| |
This CL aslo enables a presubmit check for correct formatting of all bzl files in //third_party/bazel.
PiperOrigin-RevId: 198857055
|
|
|
|
|
|
|
|
|
|
|
|
| |
...and point --experimental_distdir there, so that offline builds
are again possible out of the distribution archive.
Related #5175.
Fixes #5202.
To be cherry-picked for #5056.
Change-Id: I634296e9d83e4e18ed966b42f35acc63061259d9
PiperOrigin-RevId: 197866998
|
|
|
|
|
|
| |
and continue to use the embedded JDK as the default host_javabase.
PiperOrigin-RevId: 196471714
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 196272337
|
|
|
|
| |
PiperOrigin-RevId: 196266567
|
|
|
|
| |
PiperOrigin-RevId: 194284627
|
|
|
|
| |
PiperOrigin-RevId: 194284174
|
|
|
|
|
|
|
|
| |
We accidentally removed the .deb file, even though it's supposed to be uploaded and we didn't remove the .sig/.sha256 files of the artifacts that are *not* supposed to be uploaded.
This change fixes that.
PiperOrigin-RevId: 193651950
|
|
|
|
| |
PiperOrigin-RevId: 192137803
|
|
|
|
|
|
|
|
|
| |
Change-Id: I15159fedcc872d61d23cfe453b4af963a95d3dfb
Closes #4955.
Change-Id: I15159fedcc872d61d23cfe453b4af963a95d3dfb
PiperOrigin-RevId: 191298702
|
|
|
|
|
|
|
|
|
|
|
| |
execution.
Change-Id: Iaa5168ac8e6c13b0ac5dfc7340c0ccdfc0dcf132
Closes #4932.
Change-Id: I023c83f7373d339c2725e5a4a4b00c9d1dc1a2eb
PiperOrigin-RevId: 190828186
|
|
|
|
|
|
|
|
| |
These are the scripts I'm currently using for the Bazel 0.12.0 release.
Closes #4908.
PiperOrigin-RevId: 190598268
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The file is left as an empty file, so make upgrades easier. Site administrators can add their own content as needed, still.
Fixes #4850.
Closes #4857.
TESTED: Created a Debian VM and tested installing the new version as an upgrade and as the first Bazel, observed that the global bazelrc had the expected content.
RELNOTES: Remove the default content of the global bazelrc.
Change-Id: I5f285f0c59d18179005ffe5bfc35931299635bbb
PiperOrigin-RevId: 190060838
|
|
|
|
|
|
| |
Closes #4872.
PiperOrigin-RevId: 189889623
|
|
|
|
|
|
|
|
|
| |
repository.
Closes #4860.
Change-Id: I1689fee013d031253d5e55343be174aaa6e638c1
PiperOrigin-RevId: 189588855
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #4810, invalidates #4782, and extends #4747.
Change-Id: I19426bb30a151358875e9bae0e0c1d92b3818432
Closes #4816.
Change-Id: I5d92cec994103e2136c5ed279780f321a42d1bdd
PiperOrigin-RevId: 188722982
|
|
|
|
|
|
|
|
|
|
|
|
| |
Modeled after d6dde574ce539b11279fd4694de2304da9482a47
This is needed to remove the `METHOD_` static fields in the generated stubs, which are deprecated.
cc: @buchgr
Closes #4760.
PiperOrigin-RevId: 188182280
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit c8be465869fbcfaa00b75d241c67279324976e0b added the headless JDK
to `debian/control`, but this isn't propagating to published packages
because those use the deps list in `debian/BUILD`.
This commit adds the headless JDK to `debian/BUILD`, with comments so
future changes won't hit the same problem.
Closes #4686.
PiperOrigin-RevId: 187461399
|
|
|
|
|
|
|
|
|
|
|
| |
Tests by running Bazel commands in the current working directory.
Change-Id: I0352e206a57e677b1c87e1c842a62ca1d3558bc3
Closes #4729.
Change-Id: Ib44810ebce596e4d40786e087f57e61971e87d25
PiperOrigin-RevId: 187214804
|
|
|
|
|
|
|
|
|
|
|
| |
...so that it can use that path to compute other directories in the
output user base, in particular the default location for caches.
The first cache we will add is the hash-index cache for downloads
of external archives, but a spawn cache might be added later in the
output user base as well.
Change-Id: I24b1c33235c8f76ec008ecb1789163de2b2a45be
PiperOrigin-RevId: 187164275
|
|
|
|
|
|
|
|
|
|
|
| |
ControlFlowChecker has a precondition check that assumes nested functions do not occur. While this assumption is reasonable for a valid Skylark syntax, linter can actually be invoked on malformed files and users would get a stack trace instead of a human-readable linter error.
Alternative and possibly a better strategy would to not run CFChecker in case parse errors are detected.
fixes #4511
Closes #4512.
PiperOrigin-RevId: 185538897
|
|
|
|
| |
PiperOrigin-RevId: 183840991
|
|
|
|
|
| |
Change-Id: I33717f6a68035bfd5f8406685f935253e1d24325
PiperOrigin-RevId: 183815476
|
|
|
|
|
|
|
|
|
|
|
| |
The debian package changlog file doesn't have to contain the real CHANGELOG.md.
Parsing change log is error-prone and caused our release job to fail everytime,
so here we simplified the script for generating changelog.
Fix https://github.com/bazelbuild/bazel/issues/4530
Change-Id: I8adc5a98def5709ea57f9edbed9f0cf772a48d76
PiperOrigin-RevId: 183651058
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Change-Id: Ie6070b01e7d004589064edc1f182baa6b6fac8b4
PiperOrigin-RevId: 182940613
|
|
|
|
|
|
|
| |
...as it breaks shell tests
Change-Id: I191ec7c0f36832ff064af0b756a8c8fb41eb2a87
PiperOrigin-RevId: 182509548
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added tests for checking JavaExportsProvider state.
Refactored logic working with collection in favor of using Streams to improve readability.
All other providers will be implemented in next CLs.
previous CL with JavaCompilationArgsProvider implementation is https://github.com/bazelbuild/bazel/commit/32dff21d00ad7d1bdf50e8761d675a6e7e002de9,
JavaSourceJarsProvider : https://github.com/bazelbuild/bazel/commit/5bd53cb609480ca896ca2d011f415b424c63ce63
RELNOTES:none
PiperOrigin-RevId: 182342490
|
|
|
|
| |
Change-Id: I05fa85967317c4581081adfc620e24a7c6322669
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1.Deleted config_setting for --cpu=x64_windows_msys, because we don't build
Bazel with MSYS gcc anymore.
2.Deleted config_setting for --cpu=x64_windows_msvc, because it uses exactly
the same toolchain as --cpu=x64_windows, it'll be removed in the future.
This change reduces the complexity of our BUILD files and make them less
confusing.
Change-Id: I939831a6861413b0f745fb1be98aacd4fb780e0a
PiperOrigin-RevId: 181751853
|
|
|
|
|
|
|
|
| |
Fixes #3872
Closes #3873.
PiperOrigin-RevId: 181644101
|
|
|
|
|
|
|
|
| |
...until the bugs in the google_compute_engine scripts are fixed
upstream.
Change-Id: I3fcced5ad82735270c991f5a3595b34da60de544
PiperOrigin-RevId: 181158629
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
FreeBSD should work again, so re-enable it.
*** Original change description ***
Remove FreeBSD from our CI temporarily.
RELNOTES: None.
PiperOrigin-RevId: 181140165
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 180857355
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 180851611
|
|
|
|
|
| |
Change-Id: Ie355e9f122c074b24d119438e1f0a6e75300d1d1
PiperOrigin-RevId: 179043273
|