| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The launcher script uses "exec -a" to launch the wrapper, but if
the wrapper script is itself a Bash script, Bash will set "$0" to be
the path to the wrapper script, not the path to the launcher script.
To work around this, we've been having our wrapper script search the
user's PATH environment variable for bazel-real, but that doesn't
work well with the IntelliJ plugin for Bazel, which may not use the
expected PATH environment.
--
Change-Id: I402ad29d5b809be8e687e217e19c03e7ac3eb972
Reviewed-on: https://cr.bazel.build/7550
PiperOrigin-RevId: 140851992
MOS_MIGRATED_REVID=140851992
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now the release branch does not contains the release commit anymore.
Instead, we regenerate the full release notes each time we have to
(release candidate creation and final release).
Two side effects:
- The date is now showing the date of the operation and no longer
the date of the release candidate (so release will be correctly dated)
- The release notes show the release candidate number :)
Tested: bazel test //scripts/release/... + build README.md
--
Change-Id: Ia249bbdc0d6ed240bd969f24aa013f709f9a0a74
Reviewed-on: https://cr.bazel.build/7338
PiperOrigin-RevId: 140841432
MOS_MIGRATED_REVID=140841432
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Closes #2095.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2095
MOS_MIGRATED_REVID=140134289
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've used this to create https://chocolatey.org/packages/bazel/0.4.1-rc2-20161124-122858 which is in the queue for automated validation.
That package is built with #2134.
Closes #2135.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2135
MOS_MIGRATED_REVID=140131036
|
|
|
|
|
|
|
|
|
|
| |
See gitter chat around https://gitter.im/chocolatey/choco?at=58361d42b07a1fd34833fe36. The rc failed automatic validation because of it, we think.
Closes #2134.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2134
MOS_MIGRATED_REVID=140114046
|
|
|
|
|
|
|
|
|
|
| |
Based on [this comment](https://github.com/bazelbuild/bazel/issues/2027#issuecomment-262229811), allow python3 to be used. cc @meteorcloudy.
Closes #2122.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2122
MOS_MIGRATED_REVID=140031775
|
|
|
|
|
|
|
|
|
|
| |
find(1) defaults to not following symlinks, which doesn't work when all
the folders get replaced with symlinks.
--
Change-Id: I016db7bfefb308eb7026d2a52ba768613895dfee
Reviewed-on: https://bazel-review.googlesource.com/c/6810/
MOS_MIGRATED_REVID=139063351
|
|
|
|
|
|
|
| |
--
Change-Id: I09053cbd476e5f8bb5bdb9f272ad414d165f6d9f
Reviewed-on: https://bazel-review.googlesource.com/#/c/7131
MOS_MIGRATED_REVID=138855685
|
|
|
|
|
|
|
|
|
|
| |
This fixes #2032.
Closes #2046.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2046
MOS_MIGRATED_REVID=138377177
|
|
|
|
|
|
|
|
|
|
|
|
| |
This
- makes the `tools/*.ps1` generation more sane
- supports generating a package for RCs
Closes #2005.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2005
MOS_MIGRATED_REVID=138052483
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137500893
|
|
|
|
|
|
|
|
| |
Closes #1949.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1949
MOS_MIGRATED_REVID=137022912
|
|
|
|
|
|
|
|
|
|
|
| |
1. Update required version of msys to match versions that are published on chocolatey
2. Warn user about required possibly incompatible entries in PATH.
Closes #1933.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1933
MOS_MIGRATED_REVID=136129573
|
|
|
|
|
|
|
|
|
|
| |
Note - the chocolatey package to satisfy this has not yet been released, but it _will_ be according to [this trail](https://github.com/userzimmermann/choco-packages/issues/7#issuecomment-252605193)
Closes #1905.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1905
MOS_MIGRATED_REVID=135774603
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update `select` statements in BUILD files with the
new config_setting.
This is a first step on a long path that leads to
us being able to compile bazel on Windows with
--cpu=x64_windows_msvc. Needless to say, we're not
there yet.
Tested: on Linux, Darwin, Windows/MSYS
--
MOS_MIGRATED_REVID=134534613
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1742
MOS_MIGRATED_REVID=134283632
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
Fixes #1577
--
Change-Id: I81343d611490263bc7e16dedfbbc56f9f988f63d
Reviewed-on: https://bazel-review.googlesource.com/#/c/4170
MOS_MIGRATED_REVID=128576630
|
|
|
|
|
|
|
| |
--
Change-Id: I8c0b6adf08a4ca64ad41e0454cb30842c133fa22
Reviewed-on: https://bazel-review.googlesource.com/#/c/4161
MOS_MIGRATED_REVID=128465441
|
|
|
|
|
|
|
|
|
| |
Fixes #1540.
--
Change-Id: I0f16bde6496f2abef8ba3d3562e62a1534c177ca
Reviewed-on: https://bazel-review.googlesource.com/#/c/4081/
MOS_MIGRATED_REVID=127960571
|
|
|
|
|
|
|
|
|
| |
Also remove some bashism to fix #1456.
--
Change-Id: I374f1290a3eb9e9e5bcc48e19a1c0ab1c5bdaa99
Reviewed-on: https://bazel-review.googlesource.com/#/c/3952/
MOS_MIGRATED_REVID=126572632
|
|
|
|
|
|
|
|
|
|
|
| |
missing file to it.
We need to activate this check on presubmits
--
Change-Id: Ia95e92d3816ce92bb69bc0e2cf56e9c60b68d970
Reviewed-on: https://bazel-review.googlesource.com/#/c/3949/
MOS_MIGRATED_REVID=126404792
|
|
|
|
|
|
|
|
|
|
| |
Declare openjdk-9-jdk as Conflicts
Progress towards #1456
--
Change-Id: I67c17b78f90f81dbcc9c39bf6f3915789662fa94
Reviewed-on: https://bazel-review.googlesource.com/#/c/3951
MOS_MIGRATED_REVID=126402113
|
|
|
|
|
|
|
|
|
| |
is not picked up when you run the scripts manually using "bash script.sh".
This is also in our shell style guide: "Executables must start with #!/bin/bash and a minimum number of flags. Use set to set shell options so that calling your script as bash <script_name> does not break its functionality."
--
MOS_MIGRATED_REVID=125450962
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
This is a roll-forward of commit 009b48bcfaf4ebb17f9ab03bea9036cfa3c12ff0, making --bazelrc a no-op.
*** Original change description ***
Automated [] rollback of commit 009b48bcfaf4ebb17f9ab03bea9036cfa3c12ff0.
*** Reason for rollback ***
Broke bazel installation on ci.bazel.io, see http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel-Install/578/console
This change should make --bazelrc a non-op first to remove it.
*** Original change description ***
Remove .bazelrc
This hasn't been used in several releases.
--
MOS_MIGRATED_REVID=122998537
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke bazel installation on ci.bazel.io, see http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel-Install/578/console
This change should make --bazelrc a non-op first to remove it.
*** Original change description ***
Remove .bazelrc
This hasn't been used in several releases.
--
MOS_MIGRATED_REVID=122993255
|
|
|
|
|
|
|
| |
This hasn't been used in several releases.
--
MOS_MIGRATED_REVID=122844213
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we were not removing a potential existing symlink.
If this is a directory then the rm will fail, leading to
a failure of the installer, whereas we would create a
wrong symlink with the previous code.
Fixes #1219.
--
MOS_MIGRATED_REVID=121262370
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Along the path, fix the build for JDK 7 and get rid of
most ugliness in the JDK 7 build. Now simply setting
JAVA_VERSION to 1.7 will build a JDK 7 compatible version.
Fixes #1159.
--
Change-Id: I9599283844a57d9e053f12d37445907f22a9232e
Reviewed-on: https://bazel-review.googlesource.com/#/c/3452
MOS_MIGRATED_REVID=120332747
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks ci.bazel.io
While the basics for fixing the build is easy (just a few typos in packages building), fixing the test is a bit more tricky. I see only one solution for fixing the test: use a select statement that would select the good bazel version but that would always pull JavaBuilder as an external dependency when we do test.
Better roll this back then check the JavaBuilder 0.1.0 as a binary in third_party before rolling forward (a similar change is still needed to decouple running the test and building the binary for JDK 7)
*** Original change description ***
Refactor build for JDK 7
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
MOS_MIGRATED_REVID=119773123
|
|
|
|
|
|
|
|
|
|
|
| |
Now the JDK 7 tuning happens all in Bazel, removing logic
from the CI script. It uses remote repositories to access
JDK 7 dependencies.
--
Change-Id: Iff590c6642ca5b2343aa15096f8fd837d1c80787
Reviewed-on: https://bazel-review.googlesource.com/#/c/3327
MOS_MIGRATED_REVID=119634530
|
|
|
|
|
|
|
| |
Fixes #739.
--
MOS_MIGRATED_REVID=116257685
|
|
|
|
|
|
|
|
|
|
|
| |
It seems like the change introduced in pull request #785 does not
function universally. On some releases of Debian and Ubuntu, it looks
like packages are declared as providing java{7,8}-sdk.
Fixes #961.
--
MOS_MIGRATED_REVID=115338913
|
|
|
|
|
|
|
| |
This should fix the current ci.bazel.io breakage.
--
MOS_MIGRATED_REVID=114892993
|
|
|
|
|
|
|
|
|
| |
So that bazel can read it.
Fixes #894.
--
MOS_MIGRATED_REVID=114689351
|
|
|
|
|
|
|
| |
Fixes #887.
--
MOS_MIGRATED_REVID=114681512
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will fix some issue with loading skylark rules from @bazel_tools.
Tested with ./compile.sh all and also a project that use pkg_tar from
@bazel_tools (which is broken at HEAD).
--
Change-Id: Iffbb7134ef5fee497890c4d01b85084973d45ad0
Reviewed-on: https://bazel-review.googlesource.com/2800
MOS_MIGRATED_REVID=113508661
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=112685830
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Fixes #752.
--
MOS_MIGRATED_REVID=111614541
|