| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
| |
Fixes #4354.
Closes #4355.
PiperOrigin-RevId: 185808171
|
|
|
|
|
|
|
| |
This fixes "type 'depset' is not iterable. Use the `to_list()` method
to get a list." warning.
Change-Id: I10bd791ce15445469afb9e12b2246be583c77a4b
|
|
|
|
|
|
|
|
|
| |
The `+` operator on dicts is deprecated and will be removed. This change makes
Bazel files compatible with the new behavior.
Fixes #4346.
PiperOrigin-RevId: 180702882
|
|
|
|
|
|
| |
The `set` constructor is obsolete and will be removed in the future.
PiperOrigin-RevId: 163331591
|
|
|
|
|
| |
RELNOTES: None
PiperOrigin-RevId: 160156249
|
|
|
|
|
|
|
|
|
| |
Additional changes:
- Introduce a Skylark macro java_library_srcs that provides the source jars of a java_*_library rule.
- Remove bazel's own java_proto_library implementation.
Change-Id: I18f2259bc75ca0fb32dcd8a6a857c609bd2c7773
PiperOrigin-RevId: 158146210
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* We already have native python rules, so the skylark
ones are no longer unnecessary now
* Leaving `load skylark rules` statement in the example
may be misleading for newcomers
Testing done:
* re-compile bazel
* use it to build example folder and run py target
``` shell
./compile.sh compile /usr/bin/bazel
/home/yiyu/opt/bazel/output/bazel build //examples:all
/home/yiyu/opt/bazel/output/bazel run //examples/py:bin
```
--
Change-Id: Icd82afff2b74e77c0bcc80687b04225baf28f6ad
Reviewed-on: https://cr.bazel.build/9070
PiperOrigin-RevId: 148646895
MOS_MIGRATED_REVID=148646895
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Broke tests on CI: http://ci.bazel.io/job/bazel-tests/570/
*** Original change description ***
Roll forward execroot change
RELNOTES[INC]: Previously, an external repository would be symlinked into the
execution root at execroot/local_repo/external/remote_repo. This changes it to
be at execroot/remote_repo. This may break genrules/Skylark actions that
hardcode execution root paths. If this causes breakages for you, ensure that
genrules are using $(location :target) to access files and Skylark rules are
using http://bazel.io/docs/skylark/lib/File.html's path, dirname, etc.
functions. Cust...
--
PiperOrigin-RevId: 147833177
MOS_MIGRATED_REVID=147833177
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RELNOTES[INC]: Previously, an external repository would be symlinked into the
execution root at execroot/local_repo/external/remote_repo. This changes it to
be at execroot/remote_repo. This may break genrules/Skylark actions that
hardcode execution root paths. If this causes breakages for you, ensure that
genrules are using $(location :target) to access files and Skylark rules are
using http://bazel.io/docs/skylark/lib/File.html's path, dirname, etc.
functions. Custom crosstools that hardcode external/<repo> paths will have to
be updated.
Issue #1262.
--
PiperOrigin-RevId: 147726370
MOS_MIGRATED_REVID=147726370
|
|
|
|
|
|
|
|
|
|
|
|
| |
//third_party/protobuf:protobuf to refer to the Java proto runtime.
(second attempt)
This is the name in the upstream protobuf repo.
--
PiperOrigin-RevId: 147057949
MOS_MIGRATED_REVID=147057949
|
|
|
|
|
|
| |
--
PiperOrigin-RevId: 141438562
MOS_MIGRATED_REVID=141438562
|
|
|
|
|
|
|
|
|
| |
root package.
--
Change-Id: Ibbc4119ec65c27ad1f85a74450815195d18f5128
Reviewed-on: https://cr.bazel.build/7571
MOS_MIGRATED_REVID=140625048
|
|
|
|
|
|
|
| |
The previous solution added too many unneeded runfiles, which caused problems with our workers.
--
MOS_MIGRATED_REVID=135782773
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135689610
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=135353307
|
|
|
|
|
|
|
| |
renaming the action mnemonic in the Java Skylark rules to JavacBootstrap.
--
MOS_MIGRATED_REVID=134776087
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks all projects using Bazel, see https://ci.bazel.io
*** Original change description ***
Deprecated and removed HOST_CFG and DATA_CFG global variables.
--
MOS_MIGRATED_REVID=133005398
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132976702
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=132675557
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=126687108
|
|
|
|
|
|
|
|
| |
Those rules were moved to, respectively, https://github.com/bazelbuild/rules_rust,
https://github.com/bazelbuild/rules_jsonnet, https://github.com/bazelbuild/rules_scala, and https://github.com/bazelbuild/rules_closure.
--
MOS_MIGRATED_REVID=121834063
|
|
|
|
|
|
|
| |
gRPC is only used for intra-machine communications, for which not using crypto is perfectly fine.
--
MOS_MIGRATED_REVID=121825070
|
|
|
|
|
|
|
|
|
| |
This is mainly so that Dash can be fixed. It's not the optimal solution because then Dash will pull in the whole Bazel repository for a tiny little part of it, though. The optimal solution would be to make Bazel use WORKSPACE dependencies and then factor it out to a separate repository, but this will be good enough to unbreak Dash for the time being.
Progress toward fixing https://github.com/bazelbuild/dash/issues/12 .
--
MOS_MIGRATED_REVID=119633183
|
|
|
|
|
|
|
| |
I carefully kept the test_rules.bzl file but managed to omit the corresponding BUILD file from the embedded tools zip.
--
MOS_MIGRATED_REVID=119523076
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119518388
|
|
|
|
|
|
|
|
|
|
|
|
| |
The immmediate reason for this change is that we also need to add gRPC support to the proto rules, and we don't want to also support gRPC in a half-baked way.
This makes the Bazel binary much smaller and avoid giving false signals that we (for now) support protobuf compilation. The protobuf rules are only for compiling Bazel itself.
RELNOTES[INC]: Bazel does not embed protocol buffer-related rules anymore.
--
MOS_MIGRATED_REVID=119516246
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Breaks //src/test/shell/bazel:bazel_example_test because that relies on the protobuf rules depending on @bazel_tools . The correct solution is probably to eliminate the protobuf dependencies from @bazel_tools altogether, but let's make the continuous build green and then think.
*** Original change description ***
Update our rudimentary proto rules to be able to handle gRPC.
--
MOS_MIGRATED_REVID=119271980
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=119265313
|
|
|
|
|
|
|
| |
RELNOTES: Enable overriding attributes for Rust binaries.
--
MOS_MIGRATED_REVID=119244456
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117968196
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117801004
|
|
|
|
|
|
|
|
|
| |
This should reference the //:go_prefix rule in the repository the BUILD file
using go_* is in, not the repository where def.bzl lives (probably
@bazel_tools).
--
MOS_MIGRATED_REVID=117733799
|
|
|
|
|
|
|
|
| |
RELNOTES: Skylark rules that are available from their own repository will now
issue a warning when accessed through @bazel_tools.
--
MOS_MIGRATED_REVID=117730793
|
|
|
|
|
|
|
| |
//third_party/protobuf.
--
MOS_MIGRATED_REVID=117336377
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Version 3.2.1 has a CVSS 10.0 vulnerability. That's the worst kind of
vulnerability that exists. By merely existing on the classpath, this
library causes the Java serialization parser for the entire JVM process
to go from being a state machine to a turing machine. A turing machine
with an exec() function!
https://commons.apache.org/proper/commons-collections/security-reports.html
http://foxglovesecurity.com/2015/11/06/what-do-weblogic-websphere-jboss-jenkins-opennms-and-your-application-have-in-common-this-vulnerability/
--
MOS_MIGRATED_REVID=116309858
|
|
|
|
|
|
|
| |
Fixes #1004.
--
MOS_MIGRATED_REVID=116299622
|
|
|
|
|
|
|
| |
Issue #976
--
MOS_MIGRATED_REVID=115720030
|
|
|
|
|
|
|
| |
--
Change-Id: Id14500fa6febb9c7a58a8f093146d4d9771b44aa
Reviewed-on: https://bazel-review.googlesource.com/#/c/3007
MOS_MIGRATED_REVID=115438488
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
//src/test/shell/bazel:bazel_example_test broke because of commit a6e448253c289f3d5a353f038a5ea47227515a66,
which removed the allow_files and single_file properties of a bunch of
attributes in the belief that they were stale. However, //third_party:protoc
is in fact a filegroup and thus requires single_file.
I still think some of them are unnecessary... but because I do not yet know
all possible cases in which these are involved, and to prevent further
breakage, let's restore them all just in case. I may reevaluate this at a
later stage to clean them up.
--
MOS_MIGRATED_REVID=115297686
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=115250659
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is just for clarity and should be a no-op. Maintaining long shell
command lines embedded in genrules is not pretty.
This change is a combination of commit 8ec3866d9e5d28f6c09546269ec82731c45c28ad
and commit ffc891c4efbf498fdb8eaf4d2c922e7e7a58f99d with additional fixes.
In particular I have removed unnecessary properties from all rule
attributes, have made the rule respect any runfiles, and have reinstanted
the explicit dependency on the JDK. The latter is what fixes the breakage
we observed in #938, though it seems clear that we are missing a
dependency somewhere.
I have verified that this now works by running this change on a clean
Ubuntu 15.10 VM.
--
MOS_MIGRATED_REVID=115081830
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
Break Jenkins build.
See https://github.com/bazelbuild/bazel/issues/938
*** Original change description ***
Split out Java proto compilation logic to a helper script.
This is just for clarity and should be a no-op. Maintaining long shell
command lines embedded in genrules is not pretty.
--
MOS_MIGRATED_REVID=115048759
|
|
|
|
|
|
|
|
| |
RELNOTES[INC]: Renamed proto_java_library to java_proto_library. The former
is now deprecated and will print out a warning when used.
--
MOS_MIGRATED_REVID=115012027
|
|
|
|
|
|
|
|
|
|
| |
This fixes the build of Bazel with itself. Using ctx.file instead of
executable may yield a reference of the form external/blahblah/ which
does not exist in the file system. Using ctx.executable does point
to the right binary.
--
MOS_MIGRATED_REVID=114990955
|
|
|
|
|
|
|
|
|
|
| |
Change --closure_entry_point to the new --entry_point that is required to be used with --dependency_mode.
Remove the default --language_in=ECMASCRIPT5_STRICT. Closure Compiler now defaults to ECMASCRIPT6.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/926
MOS_MIGRATED_REVID=114980140
|
|
|
|
|
|
|
|
| |
This is just for clarity and should be a no-op. Maintaining long shell
command lines embedded in genrules is not pretty.
--
MOS_MIGRATED_REVID=114967410
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114906474
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update Closure Compiler to v20160208
Update Closure Library to v20160208
Update Closure Stylesheets to 1.1.0
Add "--language_in" and "--language_out" to closure_js_binary.bzl
With these flags users can transpile their closure_js_binary() from
ES6 to ES3.
Change "--manage_closure_dependencies" to "--dependency_mode=LOOSE"
because the former has been deprecated in Closure Compiler v20160208.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/910
MOS_MIGRATED_REVID=114898222
|
|
|
|
|
|
|
|
|
| |
This is in preparation for another change that will add a new helper script
to the tools/build_rules directory, and such script requires a BUILD rule
of its own.
--
MOS_MIGRATED_REVID=114898083
|
|
|
|
|
|
|
| |
This prevents a refactoring in said API
--
MOS_MIGRATED_REVID=114889925
|