8000 Add Pipeline For Release Image Builds by nigthknight · Pull Request #653 · secureCodeBox/secureCodeBox · GitHub
[go: up one dir, main page]
Skip to content

Add Pipeline For Release Image Builds #653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
J12934 merged 4 commits into from
Sep 21, 2021
Merged

Add Pipeline For Release Image Builds #653

J12934 merged 4 commits into from
Sep 21, 2021

Conversation

@nigthknight
Copy link
Member
@nigthknight nigthknight commented Sep 20, 2021 •
edited
Loading

@nigthknight nigthknight added ci Changes to the continuous integration setup maintenance labels Sep 20, 2021
@nigthknight nigthknight self-assigned this Sep 20, 2021
@nigthknight nigthknight force-pushed the ci/release-pipeline branch 2 times, most recently from e58e12a to d3c0390 Compare September 20, 2021 07:59
@nigthknight
Add Pipeline For Release Image Builds
f6703ff 
Our goal is to simplify the colaboration with forks.
To do so we want to ensure that the CI pipeline can be executed on a
fork easily. Pushing to an image registry requires that the owner of the
fork provides some secrets to this image registry.

To avoid this problem we decided to split the CI pipeline into a release
pipeline and a developement pipeline. The release pipeline is only
triggered on the release event and is only responsible for building and
pushing the container images. The developement pipeline handles the use
of container images internally and does not rely on any image registry.

This commits adds the initial build pipeline.

NOTICE: The event that triggeres the pipeline is still set to 'push' to
ensure that the pipeline is building the images correctly. This has to
be changed before merging into main

Signed-off-by: Yannik Fuhrmeister <yannik.fuhrmeister@iteratec.com>
@nigthknight
Change Trigger Event To 'release: released'
0f391e3 
Signed-off-by: Yannik Fuhrmeister <yannik.fuhrmeister@iteratec.com>
@nigthknight nigthknight marked this pull request as ready for review September 20, 2021 09:10
@nigthknight
Add Dashboard Importer To Pipeline
760170f 
Signed-off-by: Yannik Fuhrmeister <yannik.fuhrmeister@iteratec.com>
@nigthknight nigthknight mentioned this pull request Sep 20, 2021
Merged
@nigthknight nigthknight marked this pull request as draft September 21, 2021 07:18
@nigthknight
Update Docker Meta Action
23a96d9 
Signed-off-by: Yannik Fuhrmeister <yannik.fuhrmeister@iteratec.com>
@nigthknight nigthknight marked this pull request as ready for review September 21, 2021 07:39
@J12934 J12934 merged commit 54ed549 into main 93BE Sep 21, 2021
@J12934 J12934 deleted the ci/release-pipeline branch September 21, 2021 11:06
@snyk-bot snyk-bot mentioned this pull request Sep 27, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@J12934 J12934 J12934 approved these changes

Assignees

@nigthknight nigthknight

Labels

ci Changes to the continuous integration setup maintenance

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

🏗 Create Seperate Release Pipeline for Docker Build & Push The persistence-elastic-dashboard-importer docker image wasn't build since v2.4.0

3 participants

@nigthknight @J12934
0