Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Odilhao
Copy link
Member

@Odilhao Odilhao commented Apr 17, 2024

No description provided.

@Odilhao Odilhao force-pushed the push-container branch 6 times, most recently from d223a99 to a15ff55 Compare April 17, 2024 20:00
@Odilhao
Copy link
Member Author

Odilhao commented Apr 18, 2024

@evgeni do we have GITHUB_TOKEN enabled for this repo? I don't have admin permissions here.

Comment on lines +3 to +8
on:
push:
branches:
- master
schedule:
- cron: '5 5 * * 0'
Copy link
Member

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?

Copy link
Member Author

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.

Copy link
Member Author

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.

Copy link
Member

@ekohl ekohl Apr 23, 2024

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.

Copy link
Member Author

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.

Copy link
Member

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

@evgeni
Copy link
Member

evgeni commented Apr 18, 2024

@evgeni do we have GITHUB_TOKEN enabled for this repo? I don't have admin permissions here.

Jaja, it should "just" work. lol, I said it for EVR too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants