I followed your links and read about the Dockerhub situation, which seems a bit problematic. Therefore, I decided to see, if we could live with ghcr.io and uploaded our image there:
It shows up in the packages view on GitHub and I can also run it locally with that tag. Unfortunately, changing the Jenkinsfile (https://github.com/eclipse/sumo/blob/master/Jenkinsfile)
- name: ubuntu-sumo
was not successful. Error log:
[Normal][sumo/my-agent-pod-h5kcp-l87d3][BackOff] Back-off pulling image "ghcr.io/eclipse/eclipse-sumo-build-ubuntu:latest"
[Warning][sumo/my-agent-pod-h5kcp-l87d3][Failed] Error: ImagePullBackOff
ERROR: Unable to pull Docker image "ghcr.io/eclipse/eclipse-sumo-build-ubuntu:latest".
Check if image tag name is spelled correctly.
Do you have an idea what we might have missed? Do we need to enable ghcr.io somewhere?
From: cbi-dev <cbi-dev-bounces@xxxxxxxxxxx>
On Behalf Of Mikael Barbero
Sent: Friday, March 26, 2021 12:57 PM
To: Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>
Subject: Re: [cbi-dev] Building maven artifacts for Eclipse SUMO
See my answers inline.
I think we finally managed to get Eclipse SUMO build on Eclipse CI and deploy to repo.eclipse.org. However,
two questions are still open :
How can we configure the build-job to be triggered by every commit to the master branch on GitHub? I tried to understand the Jenkins docs, but I did not manage to get it working.
Can we get a dockerhub organization / user account for the Eclipse SUMO project to store the custom image? Should we open a bug for that?
See https://wiki.eclipse.org/CBI#Docker_Hub for instructions.
Manager — Release Engineering and Technology | Eclipse Foundation