| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
| |
Without this change you can't work on any code that's not in src/{main,test} in IntelliJ, e.g. tools like the remote_worker.
Closes #3224.
PiperOrigin-RevId: 159812248
|
|
|
|
|
|
|
|
| |
This will allow us to add new and optional flags like selecting a strategy used to spawn / wait for the child process.
No one except Bazel should be calling "process-wrapper" and I couldn't find any references, so this breaking change should be fine.
PiperOrigin-RevId: 159685867
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Compute the --host_jvm_args for the
bazel.windows_unix_root JVM flag on Windows.
After commit
9c54e2a764f0ddd2d3787aade1c530c5f43bd26c it's the
Bazel client's job to compute this JVM flag and
pass to the server, but during bootstrapping we
run Bazel in a client-less mode.
Fixes https://github.com/bazelbuild/bazel/issues/3186
Change-Id: I2facfdef7d301d8a96213b488728e3ae6aec1c33
PiperOrigin-RevId: 158972256
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the bazelrc we ship with our packages and recommend other
package maintainers to use, enable the experimental_skyframe_target_evaluator
and experimental_ui by default. Also set show_progress_rate_limit
to a value that fits with the experimental UI.
We plan to switch to those values as default (Issue #3187), and by
setting apropriate defaults in the rc-file, we encourage users to
test those settings while giving the possibility to easily roll back,
should any problems arise.
Change-Id: I456a5a34158541151a0bff61f3039b3d7e2d61b0
PiperOrigin-RevId: 158970147
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Follow-up to https://github.com/bazelbuild/bazel/commit/22b85a2a3c79c6f3aef1e0a61e485bb135be4551. This change updates paths and URLs to Bazel docs,
removing the versions/master directory and changing bazel.build/docs to
docs.bazel.build.
For clarification on the convention of the docs site, links referencing
docs.bazel.build/foo.html will be redirected to
docs.bazel.build/versions/master/foo.html. The versions/master directory will
contain the documentation pages pushed from HEAD. Once versioned documentation
is ready, then docs.bazel.build/foo.html will instead be redirected to
docs.bazel.build/x.y.z/foo.html, where x.y.z is the directory for the latest
stable Bazel version.
Follow-ups to this change:
* Add script that will be used by the daily push job that pushes the latest
documentation from HEAD to docs.bazel.build. This script will do the
following:
* Build the Jekyll tree, run jekyll build, and modify the resulting site
tree, moving the docs/ directory into versions/master.
* Add redirects for each of the site pages from the root of the site
to the corresponding page in versions/master.
* This should give us the minimum viable product for the new docs site.
* Add script for cutting a release of the docs and pushing to a new versioned
directory on the docs.bazel.build bucket.
RELNOTES: None
PiperOrigin-RevId: 158347197
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will help diagnose
https://github.com/bazelbuild/bazel/issues/2977,
which I believed to have been fixed by the release
of 0.5.0, however it seems to have failed once
more with 0.5.0, alas without knowing the actual
bootstrap bazel's version I cannot be sure.
Change-Id: I71e100c549b4ef30699efe6363b72eb792ad1c23
PiperOrigin-RevId: 158243584
|
|
|
|
|
|
|
|
| |
reading.
Closes #2794.
PiperOrigin-RevId: 158117701
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new docs/ directory in the bazel source tree will only contain the Bazel
docs site, which is hosted at docs.bazel.build. This change deletes the
marketing site and blog, which have been migrated to the bazel-website and
bazel-blog GitHub repositories respectively.
This change also updates the serve-docs.sh and ci/build.sh under scripts/ in
preparation for publishing the docs site.
Note that to help make reviews more manageable, this change is limited to
moving files to their new locations. Here are the follow-up changes:
* Update all links in docs to remove versions/master in paths and to add
correct bazel.build subdomain when linking to pages on the marketing site
or the blog.
* Set up versioned directories on GCS bucket and add tooling for versioning
docs
This change is also coordinated with
https://bazel-review.googlesource.com/c/11568/ to have the PublishSite job
publish to docs.bazel.build rather than www.bazel.build.
Issue #2397
RELNOTES: None
PiperOrigin-RevId: 157612651
|
|
|
|
|
| |
Change-Id: I24e44ce87f5e042ddddb4cdbdcdd118a2d30a5eb
PiperOrigin-RevId: 157573075
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 157572063
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/3077
Change-Id: I5f29fdec1f69bdda51fa62be695b8791a45240e9
PiperOrigin-RevId: 157559455
|
|
|
|
| |
Change-Id: I24e44ce87f5e042ddddb4cdbdcdd118a2d30a5eb
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 157463020
|
|
|
|
|
|
|
| |
Strangely enough, some clients have sed that doesn't support -E
RELNOTES: None.
PiperOrigin-RevId: 157397892
|
|
|
|
|
|
|
|
|
|
|
|
| |
This attempts to fix #3006.
This change will presumably have to be reversed once msysless binary name changes to become the default.
It would be simpler to name the default binary for being default, to avoid special casing (see https://github.com/bazelbuild/bazel/issues/3006#issuecomment-301440068).
Closes #3066.
PiperOrigin-RevId: 157390473
|
|
|
|
|
| |
Change-Id: I21c738873b2bc6b4d2e8b607e0a206589d905f86
PiperOrigin-RevId: 157271290
|
|
|
|
|
|
|
|
|
| |
Our web page has been reorganized. The instructions to compile from
source are now on a page of its own. Update the link in the error
message accordingly.
Change-Id: Ica1187a893b911eca638c5535a3f9686a661fe6f
PiperOrigin-RevId: 156731324
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 156107235
|
|
|
|
|
| |
RELNOTES: None.
PiperOrigin-RevId: 156102527
|
|
|
|
|
|
| |
bundled JDK.
PiperOrigin-RevId: 156092071
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 156068741
|
|
|
|
|
|
|
|
|
| |
ANDROID_SDK_API_LEVEL was previously set by a script that parsed that
platforms/ directory of the SDK. Now this functionality is handled by
android_sdk_repository which autodetects the available API levels.
Change-Id: Ifbbc5499444f465929b9d70bf488ff5ba3c4cded
PiperOrigin-RevId: 155747062
|
|
|
|
|
| |
Change-Id: I23e38767e18a90b2262a38bf8f4b347e06d1de8d
PiperOrigin-RevId: 155630560
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 155489021
|
|
|
|
|
|
|
|
|
|
| |
Instead just mark it as a default installer when there is
no installer with a bundled JDK.
Fixes #2969
To be cherry-picked for #2692.
PiperOrigin-RevId: 155483548
|
|
|
|
|
|
|
|
|
|
|
| |
We might be using more environment variables that the actual list.
To be cherry-picked for #2692.
Fixes #2953.
Change-Id: I9b926d48e14b2c65822770ab46f6507a5303c3d3
PiperOrigin-RevId: 155387369
|
|
|
|
|
|
|
| |
Closes #2959.
Ping #2692 for cherry-picking into Bazel 0.5.0.
PiperOrigin-RevId: 155357560
|
|
|
|
|
|
|
|
|
|
| |
We use fail pretty early in the script and not having
the fail function leads to non useful message about
the fail function not existing.
Fixes #2949.
PiperOrigin-RevId: 155186880
|
|
|
|
|
| |
Change-Id: If79da71d2939517724d92cbe470173b5d68e3019
PiperOrigin-RevId: 155075510
|
|
|
|
|
|
| |
To be cherry-picked for #2692.
PiperOrigin-RevId: 155063394
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can't yet fully bootstrap Bazel on Cygwin, but
can build Bazel from scratch. Building Bazel with
Bazel fails because gcc isn't found where it's
believed to be -- /usr/bin is a mount in Cygwin
(to /bin), not a symlink or directory.
In this change I:
- added support for the Cygwin shell as a
bootstrap platform (recognize `uname`)
- updateed the bootstrap scripts to use "windows"
as the PLATFORM string, not "mingw"
- fixed the git lookup code
- removed some hardwired msys-style path
- added a cygpath call to convert $PWD to a
mixed-style (otherwise the bootstrap script
passes --client_cwd=/cygdrive/c/... to the
server and WindowsFileSystem.java wants to make
that relative to c:/cygwin64)
See https://github.com/bazelbuild/bazel/issues/2885
Change-Id: Icc71261ea4f0c6d4a9c0846551a7977ca6020331
PiperOrigin-RevId: 154273014
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks CI because //scripts/packages/debian:bazel-bin still references //scripts/packages:bazel-real.
*** Original change description ***
Bundled JDK changes for the release process.
- Make the default Bazel release artifacts include the bundled JDK.
- Create additional Bazel release artifacts without a bundled JDK.
Change-Id: If87c986507ae8e7dbbf0e8f163dd0073a206b265
PiperOrigin-RevId: 154054435
|
|
|
|
|
|
|
|
|
|
| |
* Make quit & reload actually kill the server, to prevent bind errors.
* Added an arg to bind to $HOSTNAME, instead of just localhost, for
ease of code review.
* Makes option parsing a little more robust.
* Moves "build the jekyll tree" out of the "serve forever" loop.
PiperOrigin-RevId: 153840306
|
|
|
|
|
|
|
|
| |
- Make the default Bazel release artifacts include the bundled JDK.
- Create additional Bazel release artifacts without a bundled JDK.
Change-Id: If87c986507ae8e7dbbf0e8f163dd0073a206b265
PiperOrigin-RevId: 153718827
|
|
|
|
|
|
|
|
| |
The jar will be added in
https://bazel-review.googlesource.com/c/10050/
Change-Id: I6e8228f8dbc627cd22bab45ae8eda5b4f332cbda
PiperOrigin-RevId: 153634892
|
|
|
|
|
|
|
|
|
| |
Bazel binary installer contains empty files because of the line that wasn't removed while packaging bazel_tools inside bazel.
Fixes: https://github.com/bazelbuild/bazel/issues/2662
Change-Id: I53a1f74566c48c3458ced2d46362873a68b6bf49
PiperOrigin-RevId: 153048191
|
|
|
|
|
|
| |
Closes #2764.
PiperOrigin-RevId: 152907840
|
|
|
|
|
|
|
|
|
| |
It seems several env vars that are used by cc_configure are
not in the invalidation list and not included in the bootstrap
compile. Adding them.
Change-Id: I67f73ae09abbe9033bcbbcb4026dab04d225b699
PiperOrigin-RevId: 152139948
|
|
|
|
|
|
|
|
|
|
| |
This causes a hard-fail. I'm attempting to publish a fixed package now, but chocolatey.org is failing with a `502 Bad Gateway`. I'm talking to the chocolatey team in their gitter now.
I'll update here once I've been able to push.
Closes #2758.
PiperOrigin-RevId: 151693032
|
|
|
|
| |
PiperOrigin-RevId: 151564075
|
|
|
|
|
|
|
|
| |
--
Change-Id: Ic1632229e67bf82b69983f9614258c5fd54c12d8
Reviewed-on: https://cr.bazel.build/9390
PiperOrigin-RevId: 151422502
MOS_MIGRATED_REVID=151422502
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
--
Change-Id: I044b8c244d63232ccec7bf48556248ee2dd1c43d
Reviewed-on: https://cr.bazel.build/9515
PiperOrigin-RevId: 151019006
MOS_MIGRATED_REVID=151019006
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, a stamped bazel binary contains the actual timestamp at build
time. This means, that building bazel we either include no version
information at all, or the binary contains a not reproducible time
stamp. Both are not acceptable from the point of view of a downstream
maintainer of a bazel package, where the requirement is that the package
be reproducible, but the binary still provide sensible version information.
Fortunately, there is a suggested standard to solve this problem taking
the "current time" from the SOURCE_DATE_EPOCH environment variable, if
set, rather than the actual time.
See https://reproducible-builds.org/specs/source-date-epoch/.
Honor this proposed standard, so that bazel can reasonably be packaged
downstream. See issue #2240.
Note that we only use the environment variable in our bootstrap script;
for bazel itself we communicate that information via an appropriate
option.
--
Change-Id: I55409a117285b9a3446421179c20f4e8c59088f8
Reviewed-on: https://cr.bazel.build/9467
PiperOrigin-RevId: 150896326
MOS_MIGRATED_REVID=150896326
|
|
|
|
|
|
|
|
|
|
| |
Fixes: https://github.com/bazelbuild/bazel/issues/2677
--
Change-Id: Ie8518530dfd9a7eed41c44230e59afbd5724544b
Reviewed-on: https://cr.bazel.build/9455
PiperOrigin-RevId: 150754975
MOS_MIGRATED_REVID=150754975
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
@laszlocsomor - This addresses https://github.com/bazelbuild/bazel/issues/2449#issuecomment-278059161.
Note - this is _not_ in the 0.4.5 package, since I was waiting for that release to go out prior to this.
Closes #2690.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2690
PiperOrigin-RevId: 150745085
MOS_MIGRATED_REVID=150745085
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 150194302
MOS_MIGRATED_REVID=150194302
|
|
|
|
|
|
|
|
|
| |
Closes #2678.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/2678
PiperOrigin-RevId: 150167309
MOS_MIGRATED_REVID=150167309
|