| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
Instead bundle ijar's zipper binary so the skylark rules that depends on it
can use it from @bazel_tools.
A commit introducing windows config settings broke our appengine tutorial.
--
MOS_MIGRATED_REVID=114857080
|
|
|
|
|
|
|
| |
Accidentally removed in the previous change to this file.
--
MOS_MIGRATED_REVID=113170839
|
|
|
|
|
|
|
|
| |
We should delete the package-srcs filegroup at some point and just use the same for both
but we are about to remove the package-srcs so let just make this change for now.
--
MOS_MIGRATED_REVID=113163035
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=110280939
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=107939664
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=105876178
|
|
|
|
|
|
|
|
|
|
|
| |
This refactor a bit the docker rules to reuse the tarball construction.
Also introduce the debian archive for the release process.
RELNOTES[NEW]: Debian and tar packaging is now supported
(see tools/build_defs/pkg/README.md).
--
MOS_MIGRATED_REVID=105053604
|
|
|
|
|
|
|
| |
This is currently unused deadweight, but will be used pretty soon to access the tools directory instead the menagerie of various odd mechanism we currently use.
--
MOS_MIGRATED_REVID=104737151
|
|
|
|
|
|
|
|
|
| |
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=102567966
|
|
|
|
|
|
|
| |
A lot of build rules weren't shiped in the Bazel binary because of those missing filegroups
--
MOS_MIGRATED_REVID=102223626
|
|
|
|
|
| |
--
MOS_MIGRATED_REVID=100490916
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
tool conventions better.
--
MOS_MIGRATED_REVID=89510837
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
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
|