-
Notifications
You must be signed in to change notification settings - Fork 13
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.
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
Add Container Image release workflow #389
base: master
Are you sure you want to change the base?
Conversation
d223a99
to
a15ff55
Compare
@evgeni do we have |
on: | ||
push: | ||
branches: | ||
- master | ||
schedule: | ||
- cron: '5 5 * * 0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we have a release workflow, that runs on "tag is pushed" (https://github.com/theforeman/obal/blob/master/.github/workflows/release.yml), any reason not to hook it up there, instead of releasing on each push to master?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't push tags as much as we merge into master, that's why I did not added to this release workflow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could add a new action/job to release new tags after merging to master, not sure how you or @ehelms feels about this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think releasing more often would be a good thing. Not sure if after every commit would be a good thing though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could have a job that runs weekly and do auto-tag/release if we have a commit stashed from the week prior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd lean more to sumbitting a PR to release. It might be a bit more complicated, but I like the control. If we generalize it, I can see more repos in our org use it
Jaja, it should "just" work. lol, I said it for EVR too |
No description provided.