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

Introduce release automation #9

Open
timflannagan opened this issue Jun 6, 2022 · 5 comments
Open

Introduce release automation #9

timflannagan opened this issue Jun 6, 2022 · 5 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Milestone

Comments

@timflannagan
Copy link
Contributor

Goal: introduce automation that's responsible for creating a github release when a new tag has been pushed to this repository's git remote.

AC:

Note: This is more-or-less mirrored from rukpak/combo's release pipeline setup

  • Introduce a .goreleaser.template.yaml file
  • That template file contains references for building/pushing container images, and creating github releases
  • Add a Makefile target that installs goreleaser as a tool dependency
  • Add a Makefile target that generates a goreleaser.yaml file using envtest on that .goreleaser.template.yaml file
  • Add a Makefile target that generates a goreleaser.yaml file, and runs goreleaser with the provided arguments configuration
  • Add a GHA workflow that runs goreleaser on every PR, push to the main branch, and new tag event triggers
@timflannagan timflannagan added this to the v0.1.0 milestone Jun 6, 2022
@timflannagan timflannagan added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 6, 2022
@oceanc80 oceanc80 self-assigned this Jun 6, 2022
@github-actions
Copy link

github-actions bot commented Oct 6, 2022

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 6, 2022
@oceanc80 oceanc80 removed their assignment Oct 10, 2022
@tylerslaton
Copy link

This issue looks good and RukPak should be a good guide here for how to accomplish this. However, the one thing to keep in mind is what exactly we want the release artifact to be - a binary, yaml stream, etc.

@github-actions
Copy link

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 13, 2022
@timflannagan
Copy link
Contributor Author

@perdasilva @joelanford Just going through my open issues to see what can be closed: is this still an issue, or can it be closed?

@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 14, 2023
@github-actions
Copy link

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 13, 2023
@m1kola m1kola added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 4, 2023
@m1kola m1kola modified the milestones: v0.0.2, backlog Oct 13, 2023
@grokspawn grokspawn added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

5 participants