python-bareos: publish to PyPI.org by using Github Actions #514
Conversation
This file contains 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
joergsteffens
force-pushed
the
dev/joergs/master/github-action-publish-to-pypi
branch
from
fd0132c
to
7a116dc
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds 2 Github Action workflows.
Both create python-bareos packages and publish them at pypi.org.
Build and publish python-bareos dev packages onto https://test.pypi.org
for every change in the python-bareos subdirectory published on master.
Build and publish python-bareos packages onto https://pypi.org
for every release tag.
The required PyPI API keys are already set at this project settings.
Both workflows have been tested at https://github.com/joergsteffens/bareos/commits/dev/joergs/master/github-action-publish-to-pypi
This PR should also be backported for bareos-19.2.