-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bazel package deps incompatible with Travis JDK #1821
Comments
Is the name of the Travis JDK "oracle8jdk", I mean, if we add "oracle8jdk" as an alternative dependency, will that fix the problem? |
Closing as we do not have update since a month. |
The package name is Can we reopen this? I was able to get bazel to run using the following:
java & jdk packages installed:
|
Ideally, we could specify the list of packages that would be sufficient to satisfy Bazel, as that would allow us to drop the Using |
Actually there's another gotcha (but I'm new to this stuff, so I may be missing a trick)... the container based environment runs Ubuntu 12.04. It's possible to install bazel without sudo using the installer script with
|
Also, per the output from @justinsb above, perhaps |
Also, re: Ubuntu 12.04 (Precise) runtime environment in Travis: the default is indeed Precise, but you can also explicitly choose Ubuntu 14.04 (Trusty) if you prefer a newer one via the |
I have managed to make Bazel work with Oracle JDK8 using a # Extract of the most relevant config parameters; see below for full config
matrix:
include:
- os: linux
dist: trusty
sudo: required
language: java
addons:
apt:
sources:
- sourceline: "deb [arch=amd64] http://storage.googleapis.com/bazel-apt stable jdk1.8"
key_url: "https://storage.googleapis.com/bazel-apt/doc/apt-key.pub.gpg"
packages:
- oracle-java8-installer
- bazel See full config and successful Travis run with this config. Some explanation for the particular parameters:
I believe there's still value for adding I think the required change is quite small so I'll send a PR to fix this. |
With this change, `oracle-java7-installer` and `oracle-java8-installer` become alternatives to satisfy the JDK dependency and thus can be implicitly installed when someone just asks to install Bazel by itself. Resolves issue bazelbuild#1821.
Dagger has been pinning against a version here: https://github.com/google/dagger/blob/b15108ffbc680296d80831f68a1108d803a89426/.travis.yml#L16 But those versions seem to disappear once a new version is released, causing our build to not be hermetic. Would it be possible to leave old versions on the apt repository? |
Sorry I am late reclining the issues it was solved in between. As for CI I recommend using the artifacts from the release page instead of the apt repository. Please open a separate issue if there is more we could do. |
…a the custom apt repository, which is cleared after a new beta is released. Verified in: #772 Conversation in: bazelbuild/bazel#1821 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=158998542
…a the custom apt repository, which is cleared after a new beta is released. Verified in: #772 Conversation in: bazelbuild/bazel#1821 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=158998542
I am trying to test a project which uses Bazel with Travis.
The only way I've gotten to use it is via the following config (see full config file):
Travis includes the ability to get JDK 8 pre-installed via the following option:
However, Bazel is incompatible with the Oracle 8 JDK provided by Travis, due to package dependencies. Specifically, attempting to install Bazel from a package with Travis CI's pre-installed JDK 8 generates the following error:
It would be nice to eliminate some of the complexity of integrating with Bazel by making the Bazel package compatible with the Travis CI's Oracle 8 JDK package.
The text was updated successfully, but these errors were encountered: