tractus-x: Allow image signing through Github Actions
Summary
Provide a workflow / unlock the possibility to sign container images when using Github Actions.
What is the current bug behavior?
As far as i know we would need to use the offered Jenkins instance from the EF. Due to our whole org using Github Actions extensivly, it would be great to be able to do this directly in Github Actions were we build and test images.
What is the expected correct behavior?
Allow image signing on Github Actions / inside Githubs ecosystem.
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
We currently have 10-20 teams working on Eclipse Tractus-X (https://github.com/eclipse-tractusx) and using Github Actions for everything. Sooner than later we want to provide signed images. We probably will not do image signing if the EF Jenkins is necessary as no one is using it and this would be too much effort (managing Jenkins, maintaining Jenkins, writing Jenkins Pipelines and triggering Jenkins from Github Actions.