Project

Profile

Help

Task #4386

closed

Verify PyPI dependencies when building a release on a tag

Added by gmbnomis over 3 years ago. Updated over 1 year ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
Yes
Tags:
Sprint:
Quarter:

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
Actions #1

Updated by gmbnomis over 3 years ago

  • Description updated (diff)
Actions #2

Updated by CodeHeeler over 3 years ago

  • Tracker changed from Issue to Task
  • % Done set to 0
Actions #3

Updated by CodeHeeler over 3 years ago

  • Sprint Candidate changed from No to Yes
Actions #4

Updated by bmbouter about 3 years ago

  • Tags deleted (Pulp 3)
Actions #5

Updated by daviddavis over 1 year ago

  • Status changed from NEW to CLOSED - COMPLETE

Also available in: Atom PDF