Using Bazel with Travis-CI

[Uriel Corfa]

Hi all,

I've been using Bazel with Travis-CI for a while now. With the Beta release, this became finally usable (previously my only option was to compile Bazel during each Travis build, which took a very long time).

Here's a demo of how I make it work: https://github.com/korfuri/bazel-travis

The dummy example takes about 30 to 40s to install all dependencies, install Bazel, start Bazel, compile and run a "int main(){ return 0; }" dummy unittest. Of course since Travis doesn't keep any state between runs, all sources have to be entirely rebuilt from one run to another, so your compile/test time will depend on your entire codebase's size, not just on the changes in the commit being tested.

Feedback and PRs very welcome :)

Cheers,

Uriel

[Damien Martin-guillerez]

Thanks Uriel :)

Note that there is scripts/ci/ci.sh to recompile only the target that depends on a git changeset if you want to reduce the number of target built.

--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CADGrcx7ofJCcjF0Z_yo_Rnoubbi1%3DjmBQZ%3DDYLoLQzyqt-zEDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Uriel Corfa]

Oooh, neat. I'll integrate with that soon.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAN3hOS823ywJCuWsGzMhYxEYsUFfyOKY7NOn%3DKkNzcdv9-SA3Q%40mail.gmail.com.

[Jeff Cox]

Is there no way for Travis to keep the Bazel server alive across runs?

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CADGrcx75UdcWH8xDOn2JGCVP8awe-J-R4ut3_G%3DrGQ3fm-XdtQ%40mail.gmail.com.

[Damien Martin-guillerez]

No, their spawning a new container / vm for each build. You have to use GCE for keeping the server alive.

[Damien Martin-guillerez]

*they are spawning* sorry

[Thomas Broyer]

On Thursday, September 10, 2015 at 5:20:03 PM UTC+2, Uriel Corfa wrote:

Of course since Travis doesn't keep any state between runs,

Can't you cache some dirs? http://docs.travis-ci.com/user/caching/

Maybe at least cache the bazel installer and only download it if absent? But possibly also cache the Bazel installation, and bazel build output/state (for incremental builds; see however the other thread re. CircleCI).

[Damien Martin-guillerez]

The output base is configurable but that generally don't work well across containers.

--

You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/4082f6ba-9be1-4481-bcfe-066257f6cb86%40googlegroups.com.

[Dino Wernli]

For what it's worth, I've just gone through the exercise of adding Travis support to java-grpc-prometheus, one of my Bazel-powered projects. Here is a .travis.yml that currently works for me.

[michal.w....@gmail.com]

FYI I had success getting --output_base to work with Travis CI caching:

https://travis-ci.org/mwitkow/java-flagz/builds/168066991
here's the travis.yml: https://github.com/mwitkow/java-flagz/blob/feature/bazelify/.travis.yml