-
Notifications
You must be signed in to change notification settings - Fork 1
Add Nox task to trigger a release #378
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
Merged
ArBridgeman
merged 15 commits into
main
from
feature/#368-Add-Nox-task-for-full-release
Apr 23, 2025
Merged
Changes from all commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
02b6fb5
Add Nox task for triggering the release and function to release by a …
Jannis-Mittenzwei 27143a7
fix
Jannis-Mittenzwei 2703738
fix
Jannis-Mittenzwei b1090c9
trigger release and test
Jannis-Mittenzwei 728b117
formatting
Jannis-Mittenzwei 67c69ed
typing fix
Jannis-Mittenzwei 95bae37
doc
Jannis-Mittenzwei 7d99dd9
doc link tree problem
Jannis-Mittenzwei 6581ba3
Merge branch 'main' into feature/#368-Add-Nox-task-for-full-release
Jannis-Mittenzwei b279d1c
resolve conversation
Jannis-Mittenzwei 477adce
Merge branch 'main' into feature/#368-Add-Nox-task-for-full-release
Jannis-Mittenzwei 565c66d
Merge branch 'main' into feature/#368-Add-Nox-task-for-full-release
Jannis-Mittenzwei 4b17f5b
resolve conversation
Jannis-Mittenzwei 643b5bf
resolve conversation
Jannis-Mittenzwei 23eabf6
Update exasol/toolbox/release/__init__.py
ArBridgeman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1,5 @@ | ||
| # Unreleased | ||
|
|
||
| ## ✨ Features | ||
|
|
||
| * [#378](https://github.com/exasol/python-toolbox/pull/378/files): Add Nox task to trigger a release |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,4 +10,4 @@ | |
| ../design | ||
| plugins | ||
| modules/modules | ||
| ../user_guide/how_to_release | ||
| how_to_release | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| .. include:: ../shared_content/how_release.rst |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,52 @@ | ||
| How to Release? | ||
| =============== | ||
|
|
||
| Creating a Release | ||
| ++++++++++++++++++ | ||
|
|
||
| #. Prepare the project for a new release: | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| nox -s release:prepare -- --type {major,minor,patch} | ||
|
|
||
| #. Merge your **Pull Request** to the **default branch** | ||
|
|
||
| #. Trigger the release: | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| nox -s release:trigger | ||
|
|
||
| What to do if the release failed? | ||
| +++++++++++++++++++++++++++++++++ | ||
|
|
||
| The release failed during pre-release checks | ||
| -------------------------------------------- | ||
|
|
||
| #. Delete the local tag | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| git tag -d "<major>.<minor>.<patch>"" | ||
|
|
||
| #. Delete the remote tag | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| git push --delete origin "<major>.<minor>.<patch>" | ||
|
|
||
| #. Fix the issue(s) which led to the failing checks | ||
| #. Start the release process from the beginning | ||
|
|
||
|
|
||
| One of the release steps failed (Partial Release) | ||
| ------------------------------------------------- | ||
| #. Check the GitHub action/workflow to see which steps failed | ||
| #. Finish or redo the failed release steps manually | ||
|
|
||
| .. note:: Example | ||
|
|
||
| **Scenario**: Publishing of the release on GitHub was successfully but during the PyPi release, the upload step was interrupted. | ||
|
|
||
| **Solution**: Manually push the package to PyPi | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,79 +1 @@ | ||
| How to Release? | ||
| =============== | ||
|
|
||
| Creating a Release | ||
| ++++++++++++++++++ | ||
|
|
||
| 1. Set a variable named **TAG** with the appropriate version numbers: | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| TAG="<major>.<minor>.<patch>" | ||
|
|
||
| #. Prepare the project for a new release: | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| nox -s release:prepare -- "${TAG}" | ||
|
|
||
| #. Merge your **Pull Request** to the **default branch** | ||
| #. Switch to the **default branch**: | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| git checkout $(git remote show origin | sed -n '/HEAD branch/s/.*: //p') | ||
|
|
||
| #. Update branch: | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| git pull | ||
|
|
||
| #. Create a new tag in your local repo: | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| git tag "${TAG}" | ||
|
|
||
| #. Push the repo to remote: | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| git push origin "${TAG}" | ||
|
|
||
| .. hint:: | ||
|
|
||
| GitHub workflow **.github/workflows/cd.yml** reacts on this tag and starts the release process | ||
|
|
||
| What to do if the release failed? | ||
| +++++++++++++++++++++++++++++++++ | ||
|
|
||
| The release failed during pre-release checks | ||
| -------------------------------------------- | ||
|
|
||
| #. Delete the local tag | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| git tag -d "${TAG}" | ||
|
|
||
| #. Delete the remote tag | ||
|
|
||
| .. code-block:: shell | ||
|
|
||
| git push --delete origin "${TAG}" | ||
|
|
||
| #. Fix the issue(s) which lead to the failing checks | ||
| #. Start the release process from the beginning | ||
|
|
||
|
|
||
| One of the release steps failed (Partial Release) | ||
| ------------------------------------------------- | ||
| #. Check the Github action/workflow to see which steps failed | ||
| #. Finish or redo the failed release steps manually | ||
|
|
||
| .. note:: Example | ||
|
|
||
| **Scenario**: Publishing of the release on Github was successfully but during the PyPi release, the upload step got interrupted. | ||
|
|
||
| **Solution**: Manually push the package to PyPi | ||
| .. include:: ../shared_content/how_release.rst |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.