buildPack: maven-java11 is specified in jenkins-x.yaml but gcr.io/jenkinsxio/builder-maven is used as containers' image.
jx create spring -d web -d actuator -j 11
builder-maven-java11 is used to build.
Build failed.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project spring-test: Fatal error compiling: invalid target release: 11 -> [Help 1]
I have checked the created task and found that builder-maven is used as containers' image.
The output of jx version is:
jx 2.0.41
Kubernetes cluster v1.11.8-eks-7c34c0
kubectl v1.14.0
git git version 2.17.2 (Apple Git-113)
Operating System Mac OS X 10.13.6 build 17G6030
EKS
OS X
I guess below code are cause of the problem.
/area buildpacks
/kind bug
/priority backlog
The quickstart for java-11 fails due to this
https://github.com/jenkins-x-buildpacks/jenkins-x-kubernetes/issues/69
A workaround for this is to define the jenkins-x.yml like this
buildPack: maven-java11
pipelineConfig:
agent:
image: maven-java11
@jstrachan Maybe build pack for java 11 could have container set up to maven-java11 as per https://github.com/jenkins-x-buildpacks/jenkins-x-kubernetes/pull/16? I'm not sure why there was need for consolidation in https://github.com/jenkins-x-buildpacks/jenkins-x-kubernetes/commit/6cd979b6c543e34050164c38fe81a1a96012543f.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close
@jenkins-x-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.
Most helpful comment
A workaround for this is to define the jenkins-x.yml like this