| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Fixes #2003.
--
MOS_MIGRATED_REVID=137545010
|
|
|
|
|
|
|
|
|
|
| |
...as quite some users are more used to downloading keys
from key servers.
--
Change-Id: I6bb60a618d50c7c70561eb5851932153c470e3d2
Reviewed-on: https://bazel-review.googlesource.com/#/c/6934
MOS_MIGRATED_REVID=137526194
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added an echo to print "Created 1.2.3RC4 on branch release-1.2.3." when
`release.sh create` runs, to save people from the mistake I made (pushing the
first RC as "RC3").
I also added a line to bounce the shell back to the original branch the user
was on, since it's a bit weird to have the script exit and be on a different
branch.
--
MOS_MIGRATED_REVID=137512849
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137503749
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=137500893
|
|
|
|
|
|
|
| |
Fix https://github.com/bazelbuild/bazel/issues/1990
--
MOS_MIGRATED_REVID=137262738
|
|
|
|
|
|
|
|
|
| |
gpg need tty because it's requesting confirmation for overriding that file
Fix https://github.com/bazelbuild/bazel/issues/1990
--
MOS_MIGRATED_REVID=137251576
|
|
|
|
|
|
|
| |
RELNOTES:None
--
MOS_MIGRATED_REVID=137043040
|
|
|
|
|
|
|
| |
--
Change-Id: I6f782f5dbeba03962381d32183e2afd2f0175709
Reviewed-on: https://bazel-review.googlesource.com/#/c/6832/
MOS_MIGRATED_REVID=137029264
|
|
|
|
|
|
|
|
| |
Closes #1949.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1949
MOS_MIGRATED_REVID=137022912
|
|
|
|
|
|
|
| |
--
Change-Id: I09d8ef5daceb48066ec40420ad5cf21514059f4a
Reviewed-on: https://bazel-review.googlesource.com/#/c/6770
MOS_MIGRATED_REVID=136825145
|
|
|
|
|
|
|
| |
Will be re-added once it is fixed. Tracking bug is #1965.
--
MOS_MIGRATED_REVID=136595269
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before - failing to find completions in the relevant variable would always
force getting them fresh, regardless of whether they are present in the cache
because the `||` would always be true.
- in _bazel_get_options use a short circuit return when the variable is not
empty
- in _bazel_command, _bazel_help_topic, and _bazel_info_key nest the cache
conditions inside the if block checking for an empty varible
cleanup:
- Use the same 2 space indent for continued conditions in _bazel_get_options as
was already used in _bazel_command and the rest
Closes #1951.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1951
MOS_MIGRATED_REVID=136458728
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In our bazel-srcs tar ball, files are packed with permissions 550.
Copying into a temporary directory may preserve permissions. So,
when overwriting one of those files in the temporary directory,
grant the user write permissions before writing to that file. Otherwise,
bootstrapping from //:bazel-srcs via ./compile.sh as normal user
will fail on some systems.
--
Change-Id: I70b4645c9bc3c25b9fd356bacdb959205c64b931
Reviewed-on: https://bazel-review.googlesource.com/#/c/6695
MOS_MIGRATED_REVID=136360945
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
`gsutil rsync` does not compute checksum when one of its
argument is on a local filesystem because this can be slow,
for our use case we want to do it or two files with the same
size will be seen as identical.
--
MOS_MIGRATED_REVID=135903003
|
|
|
|
|
|
|
|
|
|
|
| |
And refer it from the various release pages.
Also:
- Adds the sig file to the release candidate page
- Fix a typo
--
MOS_MIGRATED_REVID=135793241
|
|
|
|
|
|
|
|
|
| |
Fix https://github.com/bazelbuild/bazel/issues/1668
--
Change-Id: Ibe517744cd55ad5e32420302a081cc72da878bbe
Reviewed-on: https://bazel-review.googlesource.com/#/c/6550
MOS_MIGRATED_REVID=135787988
|
|
|
|
|
|
|
|
|
|
|
| |
We have added support for Linux s390x platform in Bazel.
Closes #1891.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1891
MOS_MIGRATED_REVID=135777047
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
Bazel in the will provide a machine-readable stream of important build
events. These interfaces set up the framework and expectations about
the produced events and the entities distributing those events.
--
Change-Id: If2c3b2e11c31b0136b57eadeef2d2f8f8fe5e2e7
Reviewed-on: https://bazel-review.googlesource.com/#/c/6272
MOS_MIGRATED_REVID=134522369
|
|
|
|
|
|
|
|
|
|
| |
Since commit 94d905836c167a21d2321d26c646fde07f5fc522 we no longer need JNI for WindowsFileSystem.isJunction.
This is a partial rollback of commit 4a249b6962d32ed4cfd4165dfdae4a555b00bb69.
Affects https://github.com/bazelbuild/bazel/issues/1680
--
MOS_MIGRATED_REVID=134506403
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Current change do not include version number. Include the version
number in the artifact.
Closes #1841.
--
Change-Id: I2516527829ec28c7c9abea2424f2e7d9585af9b0
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1841
MOS_MIGRATED_REVID=134422109
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When `compile.sh` builds bazel using bazel, it
copies the resulting binary to `output/bazel`.
However sometimes the convenience symlink
`bazel-bin` is not created, probably because an
old one is still around and cannot be deleted.
That is clearly a bug, but to work around it, the
bootstrap builder shouldn't attempt to rely on the
creation of these symlinks in the first place.
This change updates compile.sh to use `bazel info`
to locate the `bazel-bin` directory's real path,
and attempt to copy the bazel binary from there.
This works around
https://github.com/bazelbuild/bazel/issues/1827
--
MOS_MIGRATED_REVID=134398451
|
|
|
|
|
|
|
|
|
| |
Those dependencies are not needed at runtime.
Fixes #1834.
--
MOS_MIGRATED_REVID=134373693
|
|
|
|
|
|
|
|
|
| |
Pass "-c opt" when building bazel.
Fixes https://github.com/bazelbuild/bazel/issues/1830
--
MOS_MIGRATED_REVID=134307054
|
|
|
|
|
|
| |
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/1742
MOS_MIGRATED_REVID=134283632
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bootstrap build is special in that it does not
use the Bazel client hence we cannot pass a
--bazelrc flag as there'd be nothing to parse it.
While Bazel is being bootstrapped it's nice to
have colors on a smart terminal, but when the
bootstrapping is done by Jenkins as part of a CI
test, we need the output to be readable, i.e. be
free of control characters, so we should pass
--colors=no for example.
By exporting BAZEL_BOOTSTRAP_STARTUP_OPTIONS the
user can control what startup flags will the
bootstrap build use, so we can pass these
dumbing-down flags during CI builds.
--
MOS_MIGRATED_REVID=134273969
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132857927
|
|
|
|
|
|
|
|
|
| |
plain grep does not avoid alias interference, it merely trades problems when "grep" is an alias for problems when "which" is an alias (both are commonly defined as aliases).
A more reliable way to turn off alias expansion is to simply quote the command name, which is what I'm doing here.
--
MOS_MIGRATED_REVID=132338563
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It now always uses mixed path style (drive letter + forward slashes) and
expands abbreviated paths (when c:\\looongpath\\foo is abbreviated to
c:\\looong~1\foo).
The result will always look like c:/looongpath/foo/.
Fixes https://github.com/bazelbuild/bazel/issues/1714
--
MOS_MIGRATED_REVID=132218638
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Still broken. :(
*** Original change description ***
Windows bootstrapping: Fix compile.sh when $TMP is unset.
Fixes https://github.com/bazelbuild/bazel/issues/1714
--
MOS_MIGRATED_REVID=132217266
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/1714
--
MOS_MIGRATED_REVID=132060993
|
|
|
|
|
|
|
| |
Fixes https://github.com/bazelbuild/bazel/issues/1680
--
MOS_MIGRATED_REVID=132051176
|
|
|
|
|
|
|
|
|
|
|
| |
We need to tell mktemp to explicitly create temporary files and
directories under TEST_TMPDIR. The default of picking up the TMPDIR
value (which may be unset) or /tmp may not work and was causing two
tests to fail. I suspect that paths outside of TEST_TMPDIR may not
be writable due to our sandboxing features.
--
MOS_MIGRATED_REVID=131957733
|
|
|
|
|
|
|
|
|
|
|
| |
of xcode to select between, relaxing the requirement that users specify --xcode_version and --ios_sdk_version even if they have only one version installed.
RELNOTES: On mac devices, detect locally installed versions of xcode to:
1. Use a sensible default if xcode is required but --xcode_version is unspecified.
2. Use sensible default iOS SDK version for the targeted version of xcode if ios_sdk_version is unspecified.
--
MOS_MIGRATED_REVID=131841587
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Re-enabling tests now that they are passing
*** Original change description ***
Disable broken tests.
--
MOS_MIGRATED_REVID=131825670
|
|
|
|
|
|
|
|
|
| |
text around the version string. Fixes #1678.
--
Change-Id: I765699c43119e28d5f0ef8245b91e263d6af6dc0
Reviewed-on: https://bazel-review.googlesource.com/c/5570
MOS_MIGRATED_REVID=131080854
|
|
|
|
|
|
|
|
|
| |
If the user had an alias grep='grep --color=always' it would break the
bash completion, outputting the formatting character. Bypass the user
alias to avoid the effect.
--
MOS_MIGRATED_REVID=131040601
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=130761732
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=130406085
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
The underlying issue (wrong operator '==' instead of '=' for test (a.k.a '[')) was fixed by commit 31b059fc07831f86be951609128b7cd51613df98 which removed the offending code completely.
*** Original change description ***
Revert build-runfiles to use /bin/bash
If /bin/sh is dash (default on Ubuntu), this output a lot of garbage error, which make thing that the dummy build-runfiles is incorrect.
See http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=ubuntu_15.10-x86_64/731/console
--
MOS_MIGRATED_REVID=129432905
|
|
|
|
|
|
|
|
|
| |
If /bin/sh is dash (default on Ubuntu), this output a lot of garbage error, which make thing that the dummy build-runfiles is incorrect.
See http://ci.bazel.io/view/Bazel%20bootstrap%20and%20maintenance/job/Bazel/JAVA_VERSION=1.8,PLATFORM_NAME=ubuntu_15.10-x86_64/731/console
--
MOS_MIGRATED_REVID=129430198
|
|
|
|
|
|
|
|
|
| |
bootstrap.
Previously, we deleted the temp dir and after that, we tried to print errfile in it, and were surprised that it didn't exist.
--
MOS_MIGRATED_REVID=129320375
|