aboutsummaryrefslogtreecommitdiffhomepage
path: root/tools/BUILD
Commit message (Collapse)AuthorAge
...
* Fix the installer and fixing the package shiped into binary version of Bazel.Gravatar Damien Martin-Guillerez2015-09-08
| | | | | -- MOS_MIGRATED_REVID=102567966
* Add missing tools directory in the filegroup to packageGravatar Damien Martin-Guillerez2015-09-03
| | | | | | | A lot of build rules weren't shiped in the Bazel binary because of those missing filegroups -- MOS_MIGRATED_REVID=102223626
* Move j2objc helper scripts into open-source Bazel.Gravatar Michael Thvedt2015-08-13
| | | | | -- MOS_MIGRATED_REVID=100490916
* Create a binary packager for BazelGravatar Damien Martin-Guillerez2015-07-29
| | | | | | | | | | | | | | | | | This packager can be called by the release scripts to generate a self-extractable bash installer for Bazel. This script was tested by hand as extra arguments can be specified to change the default install of Bazel (default is system-wide and with the argument you can make a user install). This will be the only packager for now since GitHub is offering the possibility to download the source tree as a ZIP. Hopefully, before the end of the year we could build some more package kind. -- Change-Id: I1a2d0cd39b9e4adcaf6c984ec4c855a04213b61a Reviewed-on: https://bazel-review.googlesource.com/1581 MOS_MIGRATED_REVID=99258828
* Make //src/test/shell:bazel_test work again.Gravatar Lukacs Berki2015-06-30
| | | | | | | This stubs out all Android support, but that's okay, because in order to test Android stuff, we need a way to get the NDK and the SDK somehow, which we don't know yet how to do. -- MOS_MIGRATED_REVID=97222940
* This CL adds the android_binary rule to Bazel. Gravatar Lukacs Berki2015-06-16
| | | | | | | Note that despite the rule being present, Android support is still not functional: two tools (//tools/android:{aar_generator,resources_processor} are still missing (and are a-coming!) -- MOS_MIGRATED_REVID=96099045
* Added py_test rule to BazelGravatar Damien Martin-Guillerez2015-04-17
| | | | | | | | | | | | | | py_test rule enable to use a test written in Python. A py_test is basically a py_binary that returns a non null on failure. Extraneous support is need to have nice output (see //src/test/shell/unittest.bash for the kind of support neeeded). Actually the py_test code was already there but it was just missing the necessary glue code. Also added an integration test for py_* rules in Bazel. -- MOS_MIGRATED_REVID=91407748
* Remove experimental Go support until we have a solution which fits the 'go' ↵Gravatar Han-Wen Nienhuys2015-03-25
| | | | | | | tool conventions better. -- MOS_MIGRATED_REVID=89510837
* Open-source Bazel integration testsGravatar Damien Martin-Guillerez2015-03-25
| | | | | | | | | It is a first batch of integration tests for Bazel. They tests some basic behaviors and nominal cases of Bazel rules (especially they tests the behavior of the examples provided in //examples). -- MOS_MIGRATED_REVID=89440074
* Open-source unittest.bashGravatar Damien Martin-Guillerez2015-03-18
| | | | | | | | | This is part of the shell test infrastructure for Bazel. It creates test suites in Bazel shell. Handling the test ouputs efficiently for making test summaries. -- MOS_MIGRATED_REVID=88929067
* Add symlinks to third_party/ and tools/ to base_workspaceGravatar Kristina Chodorow2015-02-19
While attempting to clean up the Bazel examples, I noticed that the example tests don't actually work because they expect a third_party directory. We could link third_party/ from the top-level bazel directory, but then we'd have crossing symlinks (base_workspace/tools->tools and third_party->base_workspace/third_party). Linking everything in one direction seemed like a better option, but alternative suggestions are welcome. -- MOS_MIGRATED_REVID=86703332