Switch docker images for CI builds to Ubuntu LTS
Our current default docker images for CI builds are:
Since CentOS switched to a rolling release (CentOS Stream), we would like to switch to Ubuntu LTS based default images. Ubuntu LTS based images are also an industry standard for CI build images (e.g. GitHub-hosted runners).
Projects are still free to use custom tailored docker images. This only affects the default images provided by each CI instance.
Please let us know if there are any concerns, questions, etc
/cc @akurtakov, @slakkimsetti, @mistria, @vchandra, @twatson, @jarthanaree, @lvogel, @jograham
Activity
added ~25796 ~24521 team:releng labels
added Awaiting Feedback label
We should be good here. @akurtakov we still use our custom centos images for native builds, native builds are not impacted by this one.
added IT-prioritylow IT-severitylow labels
added statetodo label
I have prepared new image for the Jakarta EE TCK here: https://github.com/jakartaee/platform-tck/pull/1148, just FYI, perhaps can be used as an example.
mentioned in issue #2388 (closed)
mentioned in issue #2827 (closed)
mentioned in issue #4986 (closed)
I think this is currently blocking
( FYI @thomasfroment )
From SWT perspective we need a new (non EOL) "base image" e.g the mentioned "ubuntu-latest" so we can tell consumers of SWT what to use for the future and as a new baseline (independent from GTK3/4) of their builds as otherwise we immediately will break any consumers without an easy enough alternative.
-
I just saw it here https://github.com/eclipse-cbi/jiro-agents/blob/master/README.md
but looks like not accessible right now
https://ci.eclipse.org/platform/job/eclipse.platform/job/PR-1546/1/console
Still waiting to schedule task There are no nodes with the label 'ubuntu-latest'
-
That works but seem missing something as it gets killed immediately:
https://ci.eclipse.org/platform/job/eclipse.platform/job/PR-1546/2/console
Patience, young padawan.
Let me know on which Jenkins instances you need those labels, and I will update the config for them first.
We are looking forward to feedback, which dependencies are still missing, since I was not able to find all packages that were used on the CentOS images.
-
- https://ci.eclipse.org/platform/
- https://ci.eclipse.org/pde/
- https://ci.eclipse.org/jdt/
- https://ci.eclipse.org/equinox/
- https://ci.eclipse.org/releng/
I think the most important part is java the rest should actually be provisioned by Jenkins not sure about the maven installs.
Edited by Christoph Laeubrich -
It looks good now (https://ci.eclipse.org/platform/job/eclipse.platform/job/PR-1546/):
+ mvn clean verify --batch-mode --fail-at-end -Dmaven.repo.local=/home/jenkins/agent/workspace/eclipse.platform_PR-1546/.m2/repository -Pbree-libs -Papi-check -Pjavadoc -Dmaven.test.failure.ignore=true -Dcompare-version-with-baselines.skip=false -Dmaven.compiler.failOnWarning=false -Dorg.slf4j.simpleLogger.showDateTime=true -Dorg.slf4j.simpleLogger.dateTimeFormat=HH:mm:ss.SSS -DtrimStackTrace=false Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546) Maven home: /opt/tools/apache-maven/latest Java version: 17.0.10, vendor: Eclipse Adoptium, runtime: /opt/tools/java/temurin/jdk-17/jdk-17.0.10+7 Default locale: en_US, platform encoding: ANSI_X3.4-1968just one thing, there is already Maven 3.9.9 out :-)
Edited by Christoph Laeubrich -
Those JIPPs have access to the Ubuntu pod templates, and they have access to Apache Maven 3.9.9 (the Maven version has to be specified for now, since
maven-latestdoes not yet point to 3.9.9). Would you please give access to maven 3.9.9 to m2e jipp https://ci.eclipse.org/m2e/job/m2e/job/PR-1817/7/console
-
@fgurr we see some test failing related to encodings and I noticed that
Running on ubuntu-2404-kht6f in /home/jenkins/agent/workspace/eclipse.platform_PR-1546 gives:
Default locale: en_US, platform encoding: ANSI_X3.4-1968
while Running on jipp-centos-8-agent-8gb-w7dhl in /home/jenkins/agent/workspace/eclipse.platform_master gives:
Default locale: en_US, platform encoding: UTF-8
While challenging our builds to work with unusual default encodings might be good, would it be possible to use UTF-8 as the platform encoding for the ubunut machines?
Edited by Christoph Laeubrich I've retried and it correctly shows system encoding as utf8 but still tests fail https://ci.eclipse.org/jdt/job/eclipse.jdt.debug-github/job/PR-487/3/testReport/ . Is it possible that the filesystem doesn't support utf8 file names?
if you look at https://ci.eclipse.org/releng/job/akurtakovtest/3/console locale is POSIX. It would be best ot change it to en_US.UTF-8 .
I confirm that several important matters depend on this ticket, @fgurr. If there is anything I can do to help move things forward, don't hesitate.
-
Tests are green again: https://ci.eclipse.org/jdt/job/eclipse.jdt.debug-github/job/PR-487/5/testReport/
One more missing dependency identified libwebkit2gtk-4.1. It took me sometime to figure that https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/1633 fails due to missing webkitgtk (aka no Browser implementation in SWT).
Please note that we need version libwebkit2gtk-4.1 for Gtk3 support (aka right now) but for Gtk 4 port we would need libwebkitgtk-6.0 so better to install it too.
assigned to @fgurr
