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

Release automation #13

Closed
seaneagan opened this issue Mar 31, 2021 · 5 comments
Closed

Release automation #13

seaneagan opened this issue Mar 31, 2021 · 5 comments
Assignees
Labels
Milestone

Comments

@seaneagan
Copy link
Contributor

Problem description (if applicable)
We currently have no release automation to:

  • publish semver image tags to quay
  • publish release notes

Proposed change
Add similar release automation to that of airshipctl/krm functions: airshipit/airshipctl#354

I believe the current direction is to use a single version (git tag) for all images in this repo, rather than independent versions for each image.

@seaneagan seaneagan added enhancement New feature or request triage labels Mar 31, 2021
@seaneagan seaneagan self-assigned this Mar 31, 2021
@seaneagan
Copy link
Contributor Author

airshipbot pushed a commit that referenced this issue Apr 2, 2021
Relates-To: #13
Signed-off-by: Sean Eagan <seaneagan1@gmail.com>
Change-Id: Iecfc6e4ddf456ec2bd5269829fbbf6ea9024ce83
@jezogwza jezogwza added this to the v2.1 milestone Apr 7, 2021
@eak13
Copy link

eak13 commented Apr 13, 2021

@seaneagan can we close this one?

@seaneagan
Copy link
Contributor Author

still need to do release notes automation

@eak13
Copy link

eak13 commented Apr 15, 2021

@seaneagan thanks. This was leftover from the other day before we had a chance to talk on Flight Plan. Understood.

@seaneagan
Copy link
Contributor Author

I think the plan for now is to only version the directly user facing components (airshipctl, treasuremap), so closing this.

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

No branches or pull requests

3 participants