-
Notifications
You must be signed in to change notification settings - Fork 58
Push packages to PyPi automatically #556
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
base: dev
Are you sure you want to change the base?
Conversation
Draft PR - needs testing |
inputs: | ||
notifyUsers: | | ||
andystaples@microsoft.com |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will update this to notify the core durable group
TargetFolder: $(Build.ArtifactStagingDirectory) | ||
|
||
- task: ManualValidation@1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You will want this in a separate "server" job. Jobs are "agent" by default, which take up an active slot on our agent pool. These have a timeout ceiling on them, typically about 1hr. A "server" job is limited to specific tasks but can have a significantly longer timeout.
Or you can use a deployment environment which gives another approval mechanism.
|
||
- script: | | ||
python -m twine upload --config-file $(PYPIRC_PATH) dist/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You probably want to break this out into a different pipeline entirely. Keeping it in this job will cause these builds to fail each time you reject it. So only "released" runs will report as success.
Adds pipeline steps that, after manual intervention, will upload the built package to PyPi