Pulp

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:

• Actually run the tests (i.e. run the script stage)
• Change the install script to not get dependencies from git, but from PyPI during the standard dependency resolution in pip install -e .. For example: https://github.com/gmbnomis/pulp_cookbook/blob/2c13ac22886dd13416420336ea9ac0e5072e25f9/.travis/install.sh#L13

(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