Project

Profile

Help

Story #137

closed

Story #1883: As a user, I can sync and publish all package types

As a user, I can publish repositories that contain wheel packages

Added by rbarlow about 9 years ago. Updated almost 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
2.13.0
Target Release - Python:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Currently, we only publish sdist packages. We should add the ability to publish packages that contain wheel (bdist) packages as well. Deliverables:

  • Modify the publisher to support wheel packages. There may be little to change here.
  • Write tests.
  • Write release notes.
  • Write a getting started doc example of how to use pip to install a bdist package from Pulp.

Note that #135 has the task of creating the wheel type, so it must be done first.


Related issues

Blocked by Python Support - Story #135: As a user, I can synchronize wheels from PyPICLOSED - CURRENTRELEASEamacdona@redhat.com

Actions
Actions #1

Updated by rbarlow almost 9 years ago

  • Sprint Candidate set to Yes
Actions #2

Updated by mhrivnak almost 9 years ago

  • Groomed set to Yes
Actions #3

Updated by mhrivnak almost 8 years ago

  • Sprint Candidate changed from Yes to No
Actions #4

Updated by amacdona@redhat.com almost 8 years ago

  • Parent issue set to #1883
Actions #5

Updated by amacdona@redhat.com almost 8 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to amacdona@redhat.com
Actions #6

Updated by amacdona@redhat.com almost 8 years ago

  • Status changed from ASSIGNED to MODIFIED

Once 135 was completed, this story did not require any additional changes.

Actions #7

Updated by semyers almost 8 years ago

  • Status changed from MODIFIED to POST

Added by Austin Macdonald over 7 years ago

Revision 154a56e2 | View on GitHub

Change sync code to use new model

Adds some fields that were necessary for sync, syncs in the new way, and heavily modify docblocks to explain.

closes #135

Actions #8

Updated by semyers about 7 years ago

wrote:

Once 135 was completed, this story did not require any additional changes.

I think I moved this to POST when #135 went to POST, but probably the correct solution was to close this as a duplicate? I'm not really sure what to do here. Maybe I'll just ref the same commit in #135 for this and mark this as MODIFIED, since I assume the story will help with verifying functionality?

Actions #9

Updated by semyers about 7 years ago

  • Status changed from POST to MODIFIED

2.0-dev is now being included in Platform 2.13 builds again, returning this to a testable state. Note that any smash tests related to this issue should not be run prior to 2.13.0; this is tracked in pulp-smash issue https://github.com/PulpQE/pulp-smash/issues/588.

Actions #10

Updated by pcreech almost 7 years ago

  • Platform Release set to 2.13.0
Actions #11

Updated by pcreech almost 7 years ago

  • Status changed from MODIFIED to 5
Actions #12

Updated by pcreech almost 7 years ago

  • Status changed from 5 to CLOSED - CURRENTRELEASE
Actions #13

Updated by bmbouter almost 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF