| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also sets the Bazel workspace name to io_bazel_source.
Fixes #848.
Relevant to #1116, #1124,
RELNOTES[INC]: All repositories are now directly under the x.runfiles directory in the runfiles tree (previously, external repositories were at x.runfiles/main-repo/external/other-repo. This simplifies handling remote repository runfiles considerably, but will break existing references to external repository runfiles.
---
Furthermore, if a Bazel project does not provide a workspace name in the WORKSPACE file, Bazel will now default to using __main__ as the workspace name (instead of "", as previously). The repository's runfiles will appear under x.runfiles/__main__/.
--
MOS_MIGRATED_REVID=120224534
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** Reason for rollback ***
looks like this is probably break []
*** Original change description ***
Bind path to xcrunwrapper in workspace files.
--
MOS_MIGRATED_REVID=120167193
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=120124909
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
*** 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
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=117968196
|
|
|
|
|
|
|
| |
//third_party/protobuf.
--
MOS_MIGRATED_REVID=117336377
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
They test ./compile.sh under various configuration using Docker.
Because we miss several stuff from our docker support (docker_pull and
docker_test), those test are highly unhermetic.
This only includes tests for a few OS. We will add tests for specific
use case on-demand.
--
MOS_MIGRATED_REVID=116197057
|
|
|
|
|
|
|
|
|
| |
They have now moved to https://github.com/bazelbuild/scala_rules
RELNOTES[INC]: Scala rules were deleted from the @bazel_tools repository, see https://github.com/bazelbuild/rules_scala#scala-rules-for-bazel
--
MOS_MIGRATED_REVID=115432354
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=114629930
|
|
|
|
|
|
|
|
|
| |
Tested by merging and ./compile.sh with and without the ANDROID_* environment variables.
Fixes #851.
--
MOS_MIGRATED_REVID=113962923
|
|
|
|
|
|
|
| |
--
Change-Id: Ideb2011d23da470276420afcc8b5a71f1470f391
Reviewed-on: https://bazel-review.googlesource.com/#/c/2771
MOS_MIGRATED_REVID=113639747
|
|
|
|
|
|
|
|
|
|
|
|
| |
This implements a scala_test rule analogous to the java_test rule. It uses the standard scalatest library, and adds the corresponding jar(s) to the WORKSPACE file. The rule is tested by adding a proof-of-concept test target to the scala examples.
Link to discussion thread: https://groups.google.com/d/msg/bazel-dev/5Kbbwr11XOA/znTY-H1DBgAJ
Fixes #503.
--
Reviewed-on: https://github.com/bazelbuild/bazel/pull/657
MOS_MIGRATED_REVID=113526680
|
|
|
|
|
|
|
| |
--
Change-Id: I22fb6cc5a37f5c6c216dc3abbc915d1be3fd5e6b
Reviewed-on: https://bazel-review.googlesource.com/#/c/2410/
MOS_MIGRATED_REVID=109717610
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=109405753
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=109195094
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The lack of strip_prefix lead to the files not being found with the
supplied rust.BUILD file.
Tested:
- created simple repository with rust_library and rust_binary
targets as outlined in
//tools/build_rules/rust/README.md
- (workaround) copied //tools/build_rules/rust/rust.BUILD into workspace as
suggested by @kchodorow:
https://github.com/bazelbuild/bazel/issues/488#issuecomment-143754576
- verified that library and binary build, and that binary runs
correctly
RELNOTES: Update Rust to 1.4
--
Change-Id: Ic2c275395ca245179e35e723faf0b9d13120fa1f
Reviewed-on: https://bazel-review.googlesource.com/#/c/2382/
MOS_MIGRATED_REVID=109187409
|
|
|
|
|
|
|
|
|
| |
Adds rules for csharp_binary, csharp_library, and csharp_nunit_test.
--
Change-Id: I51e448a399c535554353b3f40bf090bb602f647f
Reviewed-on: https://bazel-review.googlesource.com/#/c/2270/
MOS_MIGRATED_REVID=107399181
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107276964
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=106887522
|
|
|
|
|
|
|
| |
RELNOTES: [jsonnet] Add jsonnet_to_json_test rule for testing Jsonnet code.
--
MOS_MIGRATED_REVID=106040951
|
|
|
|
|
|
|
| |
RELNOTES: [jsonnet] Update to Jsonnet 0.8.1.
--
MOS_MIGRATED_REVID=105303487
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105076173
|
|
|
|
|
|
|
|
| |
bazel test examples/go/lib:lib_test
bazel build examples/go/bin:bin
--
MOS_MIGRATED_REVID=105070940
|
|
|
|
|
|
|
|
| |
I've got the dashboard building independent of bazel and ready to import into
https://github.com/bazelbuild/dash.
--
MOS_MIGRATED_REVID=104969804
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=104674208
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rust_test rule.
* Add rust_bench_test rule to run benchmark tests
* Add rust_doc_test rule to run Rust documentation tests.
* Enable rust_test and rust_bench_test to depend directly on a rust_library target.
* Rename rust_docs rule to rust_doc for consistency.
RELNOTES: [rust] Add rust_bench_test and rust_doc_test rules and improve usability of rust_test tule.
--
MOS_MIGRATED_REVID=104648497
|
|
|
|
|
|
|
|
|
|
|
|
| |
Additional updates to Rust rules:
* Consolidate BUILD files for Rust distribution.
* Prevent rust_binary from depending directly on cc_library.
* Update Rust version to 1.3.0
RELNOTES: [rust] Add rust_docs rule for generating rustdoc.
--
MOS_MIGRATED_REVID=103827592
|
|
|
|
|
|
|
|
|
| |
RELNOTES[NEW]: Support for build with libsass.
--
Change-Id: I2a24212d9466e2e2a8b653027f1cc9579b4d4221
Reviewed-on: https://bazel-review.googlesource.com/#/c/1990/
MOS_MIGRATED_REVID=103740130
|
|
|
|
|
|
|
| |
RELNOTES: Add Jsonnet rules to Bazel
--
MOS_MIGRATED_REVID=102895524
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=102513092
|
|
|
|
|
|
|
|
|
| |
android_{ndk,sdk}_repository rules themselves.
This is to that the Android tests also work on OS X (otherwise, we'd end up creating a file called "BUILD" in its root, which doesn't work, because it already has a directory called "build")
--
MOS_MIGRATED_REVID=102484286
|
|
|
|
|
|
|
| |
Currently only building them is tested, not running them or mobile-install, but it's still a good start.
--
MOS_MIGRATED_REVID=102237496
|
|
|
|
|
|
|
| |
crate_features to fix conflict with new default features attribute.
--
MOS_MIGRATED_REVID=101454678
|
|
|
|
|
|
|
| |
TESTED=manual
--
MOS_MIGRATED_REVID=99161344
|
|
|
|
|
|
|
| |
Time-traveling test-driven-development.
--
MOS_MIGRATED_REVID=98399070
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=97675174
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reason: there was no real reason for this, the bazel workspace link IS
always bazel-bazel.
---
Give a name to the Bazel workspace
This way the name of the workspace will always be bazel whichever the
name of the directory you are cloning in.
Especially, the bazel worskpace link will always be bazel-bazel which
is consistent with .gitignore.
--
MOS_MIGRATED_REVID=88549106
|
|
|
|
|
|
|
|
|
|
| |
This way the name of the workspace will always be bazel whichever the
name of the directory you are cloning in.
Especially, the bazel worskpace link will always be bazel-bazel which
is consistent with .gitignore.
--
MOS_MIGRATED_REVID=88546915
|
|
--
MOE_MIGRATED_REVID=85702957
|