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 Bot - release #21

Closed
richtja opened this issue Jul 24, 2024 · 0 comments · Fixed by #26
Closed

Release Bot - release #21

richtja opened this issue Jul 24, 2024 · 0 comments · Fixed by #26
Assignees

Comments

@richtja
Copy link
Contributor

richtja commented Jul 24, 2024

The release of autils will be based on a number of criteria such as a threshold of changes and the approval by maintainers.

The definition of done for this issue is to have a bot that will take those criteria into account and perform a release, including bumping the version, tagging the new version and releasing packages.

This is a continuing work after #7, which bring the automated release voting process. This issue is about automatization of release itself in the same way how it is done in avocado.


Part of #1

@richtja richtja self-assigned this Jul 24, 2024
@richtja richtja moved this to Short Term (Current Q) Backlog in Default project Jul 24, 2024
@mr-avocado mr-avocado bot moved this from Short Term (Current Q) Backlog to Triage in Default project Jul 24, 2024
@richtja richtja moved this from Triage to Short Term (Current Q) Backlog in Default project Jul 24, 2024
@richtja richtja linked a pull request Nov 15, 2024 that will close this issue
clebergnu pushed a commit that referenced this issue Nov 27, 2024
This commit creates pyproject.toml for configuration of packaging tools.
This file contains basic information about Autils for deployment to PyPi
and configuration for Autils build.

The Autils use setuptools as build backend to ensure compatibility with
Avocado. The build version is dynamic and based on git tags, it will
make easier to automate build process during testing with test.pypi.

Reference: #21
Signed-off-by: Jan Richter <[email protected]>
clebergnu pushed a commit that referenced this issue Nov 27, 2024
This is an introduction to pre-release and release wokflows.

The pre-release will build the current main branch a upload it into TEST
PyPi repo to test out the current build.

The release workflow will generate new autils major or minor input based
on the release. Then it will do the build and upload it to PyPi.

Reference: #21
Signed-off-by: Jan Richter <[email protected]>
clebergnu pushed a commit that referenced this issue Nov 27, 2024
This commit adds automatic release triggering after the release voting
has been successful. It will run the pre-release checks and if they pass
it will do the release itself.

Reference: #21
Signed-off-by: Jan Richter <[email protected]>
@github-project-automation github-project-automation bot moved this from In progress to Done 109 in Default project Nov 27, 2024
richtja added a commit that referenced this issue Nov 28, 2024
This commit creates pyproject.toml for configuration of packaging tools.
This file contains basic information about Autils for deployment to PyPi
and configuration for Autils build.

The Autils use setuptools as build backend to ensure compatibility with
Avocado. The build version is dynamic and based on git tags, it will
make easier to automate build process during testing with test.pypi.

Reference: #21
Signed-off-by: Jan Richter <[email protected]>
richtja added a commit that referenced this issue Nov 28, 2024
This is an introduction to pre-release and release wokflows.

The pre-release will build the current main branch a upload it into TEST
PyPi repo to test out the current build.

The release workflow will generate new autils major or minor input based
on the release. Then it will do the build and upload it to PyPi.

Reference: #21
Signed-off-by: Jan Richter <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done 109
Development

Successfully merging a pull request may close this issue.

1 participant