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

Automate Github release creation with a script #448

Closed
antoninbas opened this issue Feb 29, 2020 · 4 comments
Closed

Automate Github release creation with a script #448

antoninbas opened this issue Feb 29, 2020 · 4 comments
Assignees
Labels
area/build-release Issues or PRs related to building and releasing kind/design Categorizes issue or PR as related to design. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. proposal A concrete proposal for adding a feature

Comments

@antoninbas
Copy link
Contributor

Describe what you are trying to solve
I currently create each release manually by following the steps documented in https://github.com/vmware-tanzu/antrea/blob/master/docs/maintainers/release.md. This can be error-prone (and tedious), and as the project grows, there may be additional tasks to perform to create a release.

Describe the solution you have in mind
The process can be refined over time. At the moment we can just create a script to perform the tasks listed in https://github.com/vmware-tanzu/antrea/blob/master/docs/maintainers/release.md, leveraging the Github API to create the release.

In the long term, the process could look like this:

  • create a release candidate tag and push
  • run validation tests on the release tag (this only makes sense if we need to run extra tests compared to CI).
  • if tests pass, create a Github release from that release candidate. This can also be automated.
@antoninbas antoninbas added the proposal A concrete proposal for adding a feature label Feb 29, 2020
@antoninbas antoninbas self-assigned this Feb 29, 2020
@antoninbas antoninbas added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. area/build-release Issues or PRs related to building and releasing kind/design Categorizes issue or PR as related to design. labels Feb 29, 2020
@antoninbas
Copy link
Contributor Author

This is a step in the right direction: #517

@github-actions
Copy link
Contributor

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment, or this will be closed in 180 days

@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 Sep 16, 2020
@antoninbas antoninbas removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Sep 1, 2021

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment, or this will be closed in 180 days

@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 Sep 1, 2021
@antoninbas antoninbas removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 23, 2021
@github-actions
Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days

@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 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build-release Issues or PRs related to building and releasing kind/design Categorizes issue or PR as related to design. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. proposal A concrete proposal for adding a feature
Projects
None yet
Development

No branches or pull requests

1 participant