Open cdietrich opened 5 years ago
Use curl instead of wget 0.9 installs Java 11 by default, while 0.7 installs Java 8
shouldn't we have one with java 11 and java 8 to be able to set java home and run builds with both versions and java 8 as default?
I think it makes sense to create a few smaller images with clear names/tags and store them on the docker hub under the xtext namespace.
Adding this to my list for monday.
I have pushed two new images into the xtext namespace on Docker hub (for now, the Dockerfile is located in the ref projects repository.)
However, for some reason, JIRO fails to spawn a new agent for these images, while trying another image in the same podTemplate works fine. I opened a bug for this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=552266
Until this is resolved, this one is basically on hold.
any news on this?
ping @kthoms @Hejado
i guess this may be obsolete with centos image move, but we still have some jobs using smoht/xtext-buildenv
e.g ./xtext-umbrella/releng/jenkins/sign-and-deploy/Jenkinsfile ./xtext-build-tools/set-xtext-version/Jenkinsfile ./xtext-apidiff/Jenkinsfile
any update here?
move to 2.25
move to 2.26
Unassigning myself due to priorities. Re-assign if priorities change...
./xtext-apidiff/Jenkinsfile handled via eclipse/xtext#1907
grep -ri smoht/xtext-buildenv .
./xtext-umbrella/releng/jenkins/sign-and-deploy/Jenkinsfile: image: docker.io/smoht/xtext-buildenv:0.9
./xtext-build-tools/set-xtext-version/Jenkinsfile: image: docker.io/smoht/xtext-buildenv:latest # am not sure if still used
./xtext/Jenkinsfile: image: docker.io/smoht/xtext-buildenv:0.7
grep -ri smoht/xtext-buildenv .
./xtext/Jenkinsfile: image: docker.io/smoht/xtext-buildenv:0.7
i wonder if we should bump to have a moe up to date version for website
Issues with smoht/xtext-buildenv