Project

Profile

Help

Task #3614

Have Travis push packages to pypi whenever a new tag is created in the pulpcore repo

Added by daviddavis over 1 year ago. Updated 6 months ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

https://docs.travis-ci.com/user/deployment/pypi/#Deploying-tags

Because pulp/pulp includes 3 packages in one repository we will need to upload individual tags to kick off deployments.
A pulpcore-3.0.0* tag for pulpcore
A pulpcore-plugin-3.0.0* tag for pulpcore-plugin
and a pulpcore-common-3.0.0* tag for pulpcore-common


Related issues

Copied to File Support - Task #3615: Have Travis push packages to pypi whenever a new tag is created in the pulpcore repo MODIFIED Actions

Associated revisions

Revision 43e758b0 View on GitHub
Added by werwty over 1 year ago

Have Travis push packages to pypi whenever a pulp3 tags are created

closes #3614
https://pulp.plan.io/issues/3614

Revision 43e758b0 View on GitHub
Added by werwty over 1 year ago

Have Travis push packages to pypi whenever a pulp3 tags are created

closes #3614
https://pulp.plan.io/issues/3614

Revision 43e758b0 View on GitHub
Added by werwty over 1 year ago

Have Travis push packages to pypi whenever a pulp3 tags are created

closes #3614
https://pulp.plan.io/issues/3614

History

#1 Updated by daviddavis over 1 year ago

  • Copied to Task #3615: Have Travis push packages to pypi whenever a new tag is created in the pulpcore repo added

#2 Updated by bizhang over 1 year ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to bizhang

#3 Updated by bizhang over 1 year ago

@daviddavis How would the tags work when we have 2 differently versioned packages in the same repo?
pulpcore-plugin and pulpcore are versioned separately, what would a tag for this look like?

#4 Updated by bmbouter over 1 year ago

I asked in #travis, and they suggested and the `deploy:` config key accepts an array, and each array entry supports `on:` with conditions, so they think we can define multiple deploy entries that run under different conditions

https://docs.travis-ci.com/user/deployment#Conditional-Releases-with-on%3A

#5 Updated by bizhang over 1 year ago

  • Description updated (diff)

#6 Updated by bizhang over 1 year ago

  • Status changed from ASSIGNED to POST

#7 Updated by werwty over 1 year ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#8 Updated by dkliban@redhat.com about 1 year ago

  • Tags Pulp 3 added

#9 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#10 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF