Project

Profile

Help

Task #4386

Verify PyPI dependencies when building a release on a tag

Added by gmbnomis 8 months ago. Updated 6 months ago.

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

0%

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

Description

Problem

The recent release of pulpcore-plugin 0.1.0b18 has shown that the current release process is error prone. There is no automatic verification that the module is actually installable and is working.

Proposal

Change the Travis build on tag to:

(One could go even one step further and actually install the built package and test it)

Pros:

  • Increases probality that released modules can actually be installed

Cons:

  • Build process gets more intricate, since we need to model module dependencies in the build scripts:
    • pulpcore uses pulpcore-plugin and pulp_file from git
    • pulpcore-plugin uses pulpcore-plugin from PyPI and pulp_file from git
    • pulp_file and other plugins use pulpcore-plugin and pulpcore from PyPI

      (However, these dependencies do not go away just because we do not model them in the release scripting.)

  • Release process is slower and more fragile than today

History

#1 Updated by gmbnomis 8 months ago

  • Description updated (diff)

#2 Updated by CodeHeeler 8 months ago

  • Tracker changed from Issue to Task
  • % Done set to 0

#3 Updated by CodeHeeler 8 months ago

  • Sprint Candidate changed from No to Yes

#4 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF