aboutsummaryrefslogtreecommitdiffhomepage
path: root/WORKSPACE
Commit message (Collapse)AuthorAge
* Implementation of maven_jar rule in Skylark.Gravatar Jingwen Chen2016-09-23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | **Experimental** This is an initial implementation of the maven_jar rule in Skylark, targeted at the FRs in issue #1410. Implemented a wrapper around the maven binary to pull dependencies from remote repositories into a directory under {output_base}/external. Attributes `name`, `artifact`, `repository`, `sha1` have been implemented, but not `server`. Caveat: this rule assumes that the Maven dependency is installed in the system. Hence, the maven_skylark_test integration tests are tagged with "manual" and commented out because the Bazel CI isn't configured with the Maven binary yet. Added a serve_not_found helper for 404 response tests. Usage: ``` load("@bazel_tools//tools/build_defs/repo:maven_rules.bzl", "maven_jar") maven_jar( name = "com_google_guava_guava", artifact = "com.google.guava:guava:18.0", sha1 = "cce0823396aa693798f8882e64213b1772032b09", repository = "http://uk.maven.org/maven2", ) ``` With regards to server, there are some limitations with retrieving a maven_server's attribute at Loading Phase without the use of hacky macros (issue #1704), and even if macros are used, the maven_server is not treated as an actual dependency by maven_jar. There is a test (`test_unimplemented_server_attr`) to ensure that the error message to shown to users if they use the server attribute with this rule. -- Change-Id: I167f9d13835c30be971928b4cc60167a8e396893 Reviewed-on: https://bazel-review.googlesource.com/c/5770 MOS_MIGRATED_REVID=133971809
* Fix Bazel CI by appending the newline to WORKSPACE, which got lost in commit ↵Gravatar Philipp Wollermann2016-08-19
| | | | | | | | | | | 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
* java_(lite_)?proto_library to get Java proto runtimes from //external: ↵Gravatar Carmi Grushko2016-08-18
| | | | | | | instead of hard-coded values. -- MOS_MIGRATED_REVID=130543727
* Prototype for remote execution using gRPC and Netty transportGravatar Alpha Lam2016-05-16
| | | | | | | | | | | | | | | | | | | This change implements a remote worker that executes work (build or test). Bazel will be a client of the remote worker. The communication uses gRPC and Netty as transport. A single remote worker has little advantage over running locally. Additional infrastructure is needed to run workers on multiple machines and distributing the work among them. This change provides the basic building blocks for a distributed build farm. (Mainly reformatting changes compared to https://bazel-review.googlesource.com/3110, some BUILD file changes.) -- Change-Id: If7d285444ef42a6823b59443af17b61b04b9ce6a Reviewed-on: https://bazel-review.googlesource.com/#/c/3110/ MOS_MIGRATED_REVID=122376861
* Remove rust, jsonnet, scala and closure from the Bazel repositoryGravatar Damien Martin-Guillerez2016-05-09
| | | | | | | | 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
* Set Bazel's workspace nameGravatar Kristina Chodorow2016-04-27
| | | | | | | | | | RELNOTES: Bazel's workspace name is now io_bazel. If you are using Bazel's source as an external repository, then you may want to update the name you're referring to it as or you'll begin seeing warnings about name mismatches in your code. -- MOS_MIGRATED_REVID=120926179
* Bind path to xcrunwrapper in workspace files.Gravatar Cal Peyser2016-04-22
| | | | | -- MOS_MIGRATED_REVID=120558192
* Automated [] rollback of commit 857cda2c45a5cc68c3fa398311c48c571a64915d and ↵Gravatar Damien Martin-Guillerez2016-04-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | commit 790d2f6009d47fe92cf0cd92a1473bbf0141f32e. *** Reason for rollback *** Broke non-Bazel projects on ci.bazel.io Fixes #1168 *** Original change description *** Move the runfiles for external repositories to under the x.runfiles/ directory 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.... *** -- MOS_MIGRATED_REVID=120535721
* Move the runfiles for external repositories to under the x.runfiles/ directoryGravatar Kristina Chodorow2016-04-20
| | | | | | | | | | | | | | | 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
* Rollback of commit 9dc24effb614f3695c962c4e1d1012e9e2aeb453.Gravatar Cal Peyser2016-04-19
| | | | | | | | | | | | | *** Reason for rollback *** looks like this is probably break [] *** Original change description *** Bind path to xcrunwrapper in workspace files. -- MOS_MIGRATED_REVID=120167193
* Bind path to xcrunwrapper in workspace files.Gravatar Cal Peyser2016-04-19
| | | | | -- MOS_MIGRATED_REVID=120124909
* Rollback of commit 6cb8d820689ad029a9d0dc4ee1100db9b2d96515.Gravatar Damien Martin-Guillerez2016-04-14
| | | | | | | | | | | | | | | | | | | | | | *** 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
* Refactor build for JDK 7Gravatar Damien Martin-Guillerez2016-04-13
| | | | | | | | | | | 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
* Remove deprecated Skylark rulesGravatar Kristina Chodorow2016-03-24
| | | | | -- MOS_MIGRATED_REVID=117968196
* Add Python protobuf to Bazel third_party and move all protobuf targets intoGravatar David Chen2016-03-17
| | | | | | | //third_party/protobuf. -- MOS_MIGRATED_REVID=117336377
* Tests for tools/cpp:cc_configure.bzlGravatar Damien Martin-Guillerez2016-03-03
| | | | | | | | | | | | | 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
* Remove scala rules from the Bazel source treeGravatar Damien Martin-Guillerez2016-02-24
| | | | | | | | | 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
* Fixes scala workspace rules after the move to build_file_content.Gravatar Alex Humesky2016-02-15
| | | | | -- MOS_MIGRATED_REVID=114629930
* Fix ./compile.sh when no android support is presentGravatar Damien Martin-Guillerez2016-02-05
| | | | | | | | | Tested by merging and ./compile.sh with and without the ANDROID_* environment variables. Fixes #851. -- MOS_MIGRATED_REVID=113962923
* Get android path from env (fixes #746)Gravatar Steven Dee2016-02-02
| | | | | | | -- Change-Id: Ideb2011d23da470276420afcc8b5a71f1470f391 Reviewed-on: https://bazel-review.googlesource.com/#/c/2771 MOS_MIGRATED_REVID=113639747
* Add a scala_test rule to BazelGravatar Dino Wernli2016-02-02
| | | | | | | | | | | | 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
* Improve scalac: use ijar and download scalacGravatar oscar2015-12-08
| | | | | | | -- Change-Id: I22fb6cc5a37f5c6c216dc3abbc915d1be3fd5e6b Reviewed-on: https://bazel-review.googlesource.com/#/c/2410/ MOS_MIGRATED_REVID=109717610
* Use load() to add external repositories for Skylark rules.Gravatar David Chen2015-12-04
| | | | | -- MOS_MIGRATED_REVID=109405753
* [rust] Use load() to add external repositories.Gravatar David Chen2015-12-02
| | | | | -- MOS_MIGRATED_REVID=109195094
* Update Rust new_http_archive rules to use 1.4 and strip_prefixGravatar Kamal Marhubi2015-12-02
| | | | | | | | | | | | | | | | | | | | | | 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
* Add dotnet csharp support to bazel.Gravatar Jeremy Wall2015-11-10
| | | | | | | | | 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
* Reformat WORKSPACE using buildifier.Gravatar David Chen2015-11-10
| | | | | -- MOS_MIGRATED_REVID=107276964
* Make it more obvious where to look for build_tools_versions and api_level.Gravatar Carmi Grushko2015-11-03
| | | | | -- MOS_MIGRATED_REVID=106887522
* [jsonnet] Add jsonnet_to_json_test rule for testing Jsonnet code.Gravatar David Chen2015-10-22
| | | | | | | RELNOTES: [jsonnet] Add jsonnet_to_json_test rule for testing Jsonnet code. -- MOS_MIGRATED_REVID=106040951
* [jsonnet] Update to Jsonnet 0.8.1Gravatar David Chen2015-10-13
| | | | | | | RELNOTES: [jsonnet] Update to Jsonnet 0.8.1. -- MOS_MIGRATED_REVID=105303487
* Add Darwin toolchain to Go rules.Gravatar Han-Wen Nienhuys2015-10-12
| | | | | -- MOS_MIGRATED_REVID=105076173
* Provide an example for the Go rules, eg.Gravatar Han-Wen Nienhuys2015-10-09
| | | | | | | | bazel test examples/go/lib:lib_test bazel build examples/go/bin:bin -- MOS_MIGRATED_REVID=105070940
* Remove dashboardGravatar Kristina Chodorow2015-10-09
| | | | | | | | I've got the dashboard building independent of bazel and ready to import into https://github.com/bazelbuild/dash. -- MOS_MIGRATED_REVID=104969804
* Add more detail to the android integration test instructionsGravatar Kristina Chodorow2015-10-06
| | | | | -- MOS_MIGRATED_REVID=104674208
* [rust] Add rust_bench_test and rust_doc_test rules and improve usability of ↵Gravatar David Chen2015-10-05
| | | | | | | | | | | | | | 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
* Add rust_docs ruleGravatar David Chen2015-09-24
| | | | | | | | | | | | 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
* Initial checkin of sass_binary support for bazelGravatar Derek Perez2015-09-24
| | | | | | | | | RELNOTES[NEW]: Support for build with libsass. -- Change-Id: I2a24212d9466e2e2a8b653027f1cc9579b4d4221 Reviewed-on: https://bazel-review.googlesource.com/#/c/1990/ MOS_MIGRATED_REVID=103740130
* Add Jsonnet rules to Bazel.Gravatar David Chen2015-09-14
| | | | | | | RELNOTES: Add Jsonnet rules to Bazel -- MOS_MIGRATED_REVID=102895524
* Add initial D rules to Bazel.Gravatar David Chen2015-09-08
| | | | | -- MOS_MIGRATED_REVID=102513092
* Remove BUILD.glob and incorporate the necessary filegroups into the ↵Gravatar Lukacs Berki2015-09-08
| | | | | | | | | 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
* Add an integration test for Android rules.Gravatar Lukacs Berki2015-09-03
| | | | | | | Currently only building them is tested, not running them or mobile-install, but it's still a good start. -- MOS_MIGRATED_REVID=102237496
* Update Rust rules to use Rust 1.2.0. Rename features attribute toGravatar David Chen2015-08-26
| | | | | | | crate_features to fix conflict with new default features attribute. -- MOS_MIGRATED_REVID=101454678
* Add tools dependencies for Rust rules.Gravatar David Chen2015-07-27
| | | | | | | TESTED=manual -- MOS_MIGRATED_REVID=99161344
* Add tests for dashGravatar Kristina Chodorow2015-07-17
| | | | | | | Time-traveling test-driven-development. -- MOS_MIGRATED_REVID=98399070
* Basic dashboard for build resultsGravatar Kristina Chodorow2015-07-07
| | | | | -- MOS_MIGRATED_REVID=97675174
* Rolling-back giving a name to the Bazel workspaceGravatar Damien Martin-Guillerez2015-03-16
| | | | | | | | | | | | | | | | 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
* Give a name to the Bazel workspaceGravatar Damien Martin-Guillerez2015-03-16
| | | | | | | | | | 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
* Update from Google.Gravatar Han-Wen Nienhuys2015-02-25
-- MOE_MIGRATED_REVID=85702957
generated by cgit v1.2.3 (git 2.39.1) at 2024-10-30 07:58:58 +0000