I’ve tried removing/adding the JAVA and MAVEN environment options,and nothing seems to make a different in my build.Īny information on why this process is being killed or how to fix it would be great. Here is a sample config from the link I posted above: version: 2 jobs: build: workingdirectory. Here's the list of available Docker images. Robolectric deals with this using circleci/openjdk:9.0. If we were to bump the OpenJDK version for this image, the next 'LTS' (so to speak). In this way we have greater control when the image is updated and we can ensure that the installed version of Chrome is compatible with ChromeDriver used in our tests. Or something of the sort that has Android SDK pre-installed. The circleci/android:api-29 Docker image uses Java 8. We should create a custom image based on circleci/openjdk:8-jdk or circleci/openjdk:8-jdk-stretch and install the newest version of Chrome ourselves.
Per documentation it should be: docker: - image: circleci/android:api-25-alpha. Git config -global user.email config -global user.name "CircleCI" Looks like you aren't using correct Docker image for Android. Shouldn’t this image be updated much more frequently, to have up-to-date versions of the evergreen browsers in the image Thanks. The last update of the image was made 6 months ago. My config is currently: # Java Maven CircleCI 2.0 configuration file I’m using the image circleci/openjdk:8-jdk-browsers in my build, and since the release of karma-chrome-launcher 3.1.0, the build fails because it can’t start Chrome anymore. scripts/remap.sh: line 79: 377 Killed java -jar "$workdir/BuildData/bin/SpecialSource-2.jar" map -i "$jarpath.jar" -m "$classmappings" -o "$jarpath-cl.jar" I have a series of scripts that I run as a workflow job, and one of those scripts requires a jar to be executed, however CircleCI is for some reason killing the java task/process a few seconds into its execution.
0 kommentar(er)
