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

Publish to Test PyPI from Travis CI jobs #150

Merged
merged 11 commits into from
Oct 26, 2019

Conversation

MaxTyulin
Copy link
Contributor

What do these changes do?

Perform auto-publishing new dev dists to Test PyPI.

Are there changes in behavior for the user?

Related issue number

Resolves #110

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • Add a new news fragment into the CHANGES folder
    • name it <issue_id>.<type> (e.g. 588.bugfix)
    • if you don't have an issue_id change it to the pr id after creating the PR
    • ensure type is one of the following:
      • .feature: Signifying a new feature.
      • .bugfix: Signifying a bug fix.
      • .doc: Signifying a documentation improvement.
      • .removal: Signifying a deprecation or removal of public API.
      • .misc: A ticket has been closed, but it is not of interest to users.
    • Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.

@MaxTyulin
Copy link
Contributor Author

BTW, you need to specify user/password for test pypi account.

@MaxTyulin
Copy link
Contributor Author

@webknjaz @Arfey is something wrong with this PR?

.travis.yml Outdated Show resolved Hide resolved
.travis.yml Outdated Show resolved Hide resolved
.travis.yml Outdated Show resolved Hide resolved
@webknjaz webknjaz changed the title Publishing to Test PyPi implementation Publishing to Test PyPI implementation Oct 25, 2019
setup.cfg Outdated Show resolved Hide resolved
setup.cfg Outdated Show resolved Hide resolved
.travis.yml Outdated Show resolved Hide resolved
.travis.yml Outdated Show resolved Hide resolved
@webknjaz
Copy link
Member

Great, thanks! We also need to use an API token for normal PyPI: #157. (via a separate PR)

@webknjaz webknjaz changed the title Publishing to Test PyPI implementation Publish to Test PyPI from Travis CI jobs Oct 26, 2019
@webknjaz webknjaz merged commit 4d933d8 into aio-libs:master Oct 26, 2019
@webknjaz
Copy link
Member

Now, let's check out how it works: https://travis-ci.com/aio-libs/create-aio-app/jobs/249825060

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement auto-publishing new dev dists to Test PyPI on each push to master
2 participants