| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
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
|
|
|
|
|
| |
Change-Id: Ie6070b01e7d004589064edc1f182baa6b6fac8b4
PiperOrigin-RevId: 182940613
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/3761
Closes #4015.
PiperOrigin-RevId: 176340908
|
|
|
|
|
| |
Change-Id: I3fce66ec2e63d152aafc0cf9ea067d6dbf1245f7
PiperOrigin-RevId: 167484075
|
|
|
|
|
| |
Change-Id: I37bb40cae9d8a6ca99460df83b33541972926766
PiperOrigin-RevId: 164726294
|
|
|
|
|
|
|
|
|
| |
Update the documentation to instruct explicitly installing JDK 8.
Fixes #3147
Change-Id: If92ff93b095bead043c9b069e000b7afbc0abca0
PiperOrigin-RevId: 161387193
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that should not break CI this time...
- Make the default Bazel release artifacts include the bundled JDK.
- Create additional Bazel release artifacts without a bundled JDK.
Tested by running "bazel build //scripts/..." in a clean checkout and
one with this patch in, then diffing the entire bazel-out folder and
manually inspecting the resulting files (zips, tar.gz, deb, rpm) to make
sure that they contain the right files. Looks all good now, so let's try
again.
PiperOrigin-RevId: 154544164
|
|
|
|
|
|
|
|
|
|
|
|
| |
To be cherry-picked for #2472.
Fixes #2605.
--
Change-Id: Idfd1bf264ceb696ca766268c8a16891476ee33b1
Reviewed-on: https://cr.bazel.build/9111
PiperOrigin-RevId: 148749784
MOS_MIGRATED_REVID=148749784
|
|
|
|
|
|
|
|
| |
--
Change-Id: I8c6d5cdbe9e2fc19ca6a626bea26944efa36e4db
Reviewed-on: https://cr.bazel.build/8550
PiperOrigin-RevId: 146120078
MOS_MIGRATED_REVID=146120078
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As more package options are added, it's confusing that the
debian package is generated in scripts/package/BUILD, but
scripts/package/debian/ contains the related files (and isn't
itself a Bazel package). This change makes the file locations
more predictable, and also makes it easier to see what
is happening in scripts/packages.
--
Change-Id: Id8c445fc164a1a4aa09c52559a5143578cfdea88
Reviewed-on: https://cr.bazel.build/8510
PiperOrigin-RevId: 146003934
MOS_MIGRATED_REVID=146003934
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this change, `oracle-java7-installer` and `oracle-java8-installer` become
alternatives to satisfy the JDK dependency and thus can be implicitly installed
when someone just asks to install Bazel by itself.
Resolves issue #1821.
Closes #2137.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2137
MOS_MIGRATED_REVID=140200795
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137500893
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Roll-forward with appropriate fixes: --action_env is a "build" option,
not a "common" option. Moreover, also inherit the corresponding variables
for tests from the effective action environment.
Also fix the corresponding error in the design document.
*** Original change description ***
Automated [] rollback of commit 96d46280bc5a4803ba2242a4ad16939f85a3b212.
*** Reason for rollback ***
Broke installation on latest release.
Fixes #1846
*** Original change description ***
Reintroduce .bazelrc and set --action_env defaults
Shipping a .bazelrc was removed in 009b48bcfaf4ebb17f9ab03bea9036cfa3c12ff0.
However, as per our "Specifying environment variables for actions" design
document, we want to ship a global rc file specifying the common environment
variables to be inherited. So revert that change and add the desired entries
to the global bazelrc file we're shipping.
***
--
MOS_MIGRATED_REVID=134769063
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke installation on latest release.
Fixes #1846
*** Original change description ***
Reintroduce .bazelrc and set --action_env defaults
Shipping a .bazelrc was removed in 009b48bcfaf4ebb17f9ab03bea9036cfa3c12ff0.
However, as per our "Specifying environment variables for actions" design
document, we want to ship a global rc file specifying the common environment
variables to be inherited. So revert that change and add the desired entries
to the global bazelrc file we're shipping.
--
MOS_MIGRATED_REVID=134450299
|
|
|
|
|
|
|
|
|
| |
Those dependencies are not needed at runtime.
Fixes #1834.
--
MOS_MIGRATED_REVID=134373693
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Shipping a .bazelrc was removed in 009b48bcfaf4ebb17f9ab03bea9036cfa3c12ff0.
However, as per our "Specifying environment variables for actions" design
document, we want to ship a global rc file specifying the common environment
variables to be inherited. So revert that change and add the desired entries
to the global bazelrc file we're shipping.
--
Change-Id: Ib763677a951e1264ae92954df9b831374594d8b7
Reviewed-on: https://bazel-review.googlesource.com/#/c/6113
MOS_MIGRATED_REVID=133704608
|
|
|
|
|
|
|
| |
--
Change-Id: I70c5707db557637894054c0ccec98999d043c7bf
Reviewed-on: https://bazel-review.googlesource.com/#/c/4220
MOS_MIGRATED_REVID=128979317
|
|
|
|
|
|
|
| |
--
Change-Id: I8c0b6adf08a4ca64ad41e0454cb30842c133fa22
Reviewed-on: https://bazel-review.googlesource.com/#/c/4161
MOS_MIGRATED_REVID=128465441
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Issue that caused the rollback (#819) is resolved
*** Original change description ***
Automated [] rollback of [].
*** Reason for rollback ***
Prerequisite for rolling back j2objc base workspace change
*** Original change description ***
Remove base_workspace from bazel setup
I also removed a couple places the documentation referred to it incorrectly.
There are still a couple of blog posts that mention it, but that seemed okay.
RELNOTES: A bazelrc with --package_path set is no longer required for Bazel to
find its tools. This also means that building //......
--
MOS_MIGRATED_REVID=113259357
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Prerequisite for rolling back j2objc base workspace change
*** Original change description ***
Remove base_workspace from bazel setup
I also removed a couple places the documentation referred to it incorrectly.
There are still a couple of blog posts that mention it, but that seemed okay.
RELNOTES: A bazelrc with --package_path set is no longer required for Bazel to
find its tools. This also means that building //... should work to build
everything in the workspace without including Bazel's own targets.
--
MOS_MIGRATED_REVID=113164089
|
|
|
|
|
|
|
|
|
|
|
|
| |
I also removed a couple places the documentation referred to it incorrectly.
There are still a couple of blog posts that mention it, but that seemed okay.
RELNOTES: A bazelrc with --package_path set is no longer required for Bazel to
find its tools. This also means that building //... should work to build
everything in the workspace without including Bazel's own targets.
--
MOS_MIGRATED_REVID=112604261
|
|
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
|