You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CICD Pipeline Build for all Scanner, Hooks and integration-tests are based on makefile targets
Long Read:
A while ago, we introduced Makefiles to simplify the process of building and testing for all of our project components.
These Makefiles were also required to redesign the CI workflow in a maintainable way and to get rid of all the unnecessary pushes to DockerHub on every push.
For migrating scanners, there is already a new job introduced in the ci.yaml containing most of the scanners in PR #712.
To finish the migration, the following steps need to be done:
This should also resolve #940 (duplication of integration-tests target). See discussion in #712 for what the reason for the duplication was, and what the goal state would be.
Everything seems to be fixed. Not sure if the last aspect Cache Images for demo-targets is relevant any more 🤔
If so, we could raise a new issue for that later on.
Activity
malexmave commentedon Jan 27, 2022
This should also resolve #940 (duplication of
integration-teststarget). See discussion in #712 for what the reason for the duplication was, and what the goal state would be.Thanks @EndPositive for pointing this out :).
[-]CI Migration To Makefile Builds[/-][+]CI Migration To use Makefile Builds[/+][-]CI Migration To use Makefile Builds[/-][+][Epic] CI Migration To use Makefile Builds[/+]Demo-target build process moved to release pipeline
rfelber commentedon Apr 19, 2022
Everything seems to be fixed. Not sure if the last aspect
Cache Images for demo-targetsis relevant any more 🤔If so, we could raise a new issue for that later on.