Parsely/pykafka

Build and upload PyPI artifacts from Travis build

Open

#867 opened on Sep 18, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (1,114 stars) (231 forks)batch import
enhancementhelp wanted

Description

The "push to PyPI" step described here should be automated. Whenever a commit is made to master whose name indicates that it should be a new version, the Travis build for that commit should end with the indicated version being checked out and uploaded to PyPI.

Contributor guide

Tech stack
pythonshell
Domain
ci cdrelease
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Python packagingTravis CIshell scripting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Review the release process described in CONTRIBUTING.rst. Identify how to detect a version commit (e.g., by commit message pattern). Configure Travis CI to run twine upload on that condition. Check if a PyPI API token needs to be added as an encrypted environment variable.