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.

Sign up for GitHub

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

Jump to bottom

add automatic PyPI deployment #75

Merged
merged 4 commits into from
Nov 11, 2019
Merged

add automatic PyPI deployment #75

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a37f46e
add automatic PyPI deployment
ltalirz Nov 7, 2019
c72a55e
restrict deployments to master branch
ltalirz Nov 8, 2019
73618fc
Merge branch 'master' into add-pypi-deployment
ltalirz Nov 8, 2019
44f225d
Merge branch 'master' into add-pypi-deployment
ml-evs Nov 11, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
30 changes: 30 additions & 0 deletions .travis.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,3 +22,33 @@ script:
# check whether generated schema matches the committed version
- .ci/openapi_diff.sh
- codecov --token=$CODECOV_TOKEN

# Automatically deploy tags to PyPI
jobs:
include:
- stage: deploy
# Make sure the tag is valid semver
if: "tag =~ ^v[0-9]+\\.[0-9]+\\.[0-9]+(a|b|rc)?[0-9]*$"
services: ignore
addons: skip
python: 3.7
before_install: skip
install: skip
before_script: skip
script: skip
env: ignore
before_deploy:
- echo "About to deploy $TRAVIS_TAG to PyPI"
after_deploy:
- echo "Deployed $TRAVIS_TAG to PyPI"
# See https://docs.travis-ci.com/user/deployment/pypi/
deploy: &pypi
provider: pypi
skip_existing: true
user: "__token__"
password:
secure: jydagLMQt10k0l/XlVqYznqnfRpXDsnrPIDzxREBMwnoCWBvx7a+X/pEg2wFWMD3uY3/Qhev8dr6+RBgX0t1N0si4TpBMFKGkilMebRbHkkbdgRA19NSQTdgj3jml+3K095i1LO8xR7bSfn/XHZ+oN02EDdhCGEDnCLMoG9AGKLX0w/8lNu4clQxHMQ2hSTeT9imJrD6kZDDTJwMS6twF6QLwE7YowfaPRlqIn6EYjQJjDYLE6Px95v9WBeCdNuL6Yr+ojO8uiQvmj1WdpnxVG1LBYtpx3R5cb2bbj/Q8WAYniXmJGeB0lnOMqtmbDire3kZcn40JfJMJ47bNY79APkQqTylxByv1NomeCf3h4UQ0Ylr3kaKufif+PCixl7yG1YUrnOeE2Rzvtr9YyN9uJ8solpVooOtKnwWQwCkS/pcyi8h2CyfdSBLDlWai7ShkQHRCf2YDqxctyPbqaSar6ezUwT1lKtaFNdPaNfl6Au/PVJMr0ANp3Bfl74EXzoajzc9SlJBbAg/CRTbGq+Mfa8hZUtMwkSJCGcrcqz18x6rlTek/p/fmic8fdVjLSiD4V75q2r6ZrHT7OvmHUxDJ4JA4GwuWFMLNC4813ydXaC+rk3h4MxRnskSVs1v5YcBnb/7DudVWQa6ZAAOesbjqRtj8RfMLWrxW8BvBUUwKyI=
on:
repo: Materials-Consortia/optimade-python-tools
all_branches: true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to push all branches or just master?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

from my experience this can be useful for alpha/beta releases that one does not yet want to merge into master, but it comes from the gitflow model where you would have a develop branch for this.
up to you, I can also restrict it to master.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just worry that everyone has push access to arbitrary branches except master at the moment, (maybe even to master, need to check), so someone could hijack the PyPI version with unreviewed code. (I'd also be fine with moving to the gitflow model!)

tags: true