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

Auto deploy new tagged releases to PyPI #593

Merged
merged 2 commits into from Mar 28, 2018

Conversation

Projects
None yet
3 participants
@stefankoegl
Copy link
Member

stefankoegl commented Feb 25, 2018

This pull request implements automatic deployment of tagged commits to PyPI.

The upload is triggered by Travis-CI. See the documentation for more information on this feature.

For this purpose I have created a new PyPI user soco-bot, and added it as a maintainer for the soco project there. Please let me know if I should add additional email addresses to this user, to avoid being the single point of failure for recovering access to the account.

This change would (slightly) reduce the effort of doing a release, and would lower the entry barrier for doing so.

@stefankoegl stefankoegl force-pushed the auto-deploy branch from 84a76b6 to 88f35cd Feb 25, 2018

@stefankoegl stefankoegl merged commit 1382931 into master Mar 28, 2018

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@stefankoegl stefankoegl referenced this pull request Mar 28, 2018

Closed

Release Notes 0.15 #578

@stefankoegl stefankoegl deleted the auto-deploy branch Mar 28, 2018

@KennethNielsen

This comment has been minimized.

Copy link
Member

KennethNielsen commented Apr 3, 2018

@stefankoegl looks great. What is the safety like for this functionality?

@stefankoegl

This comment has been minimized.

Copy link
Member

stefankoegl commented Apr 18, 2018

It essentially means everyone who can push to master can trigger a release. I did not see this as a concern, as we have gaven out permissions quite selectively anyway. Is this a concern for you, or do you see any other issues?

@stefankoegl stefankoegl added this to the 0.15 milestone May 13, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment