Project

Profile

Help

Story #4198

Story #4188: As a Pulp3 user, I have containers

As a plugin writer, the plugin_template has a container-build-test pipeline as part of it

Added by bmbouter about 1 year ago. Updated 7 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:
No
Tags:
Plugin Template
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

The plugin template needs machinery that makes it easy for the plugin writer to setup a Travis build+test+publish pipeline for plugins.

This machinery should run when a release tag is pushed indicating a new release, similar to how plugins publish to PyPI already. When activated it should:

1. Install the plugin on top of the generic, most recent core container.
2. start that container and run pulp-smash tests against it
3. If all the tests pass, publish the container to quay.io with credentials

The credentials need to be configured somehow in the config files.

History

#1 Updated by bmbouter about 1 year ago

  • Parent task set to #4188

#2 Updated by bmbouter about 1 year ago

  • Project changed from Pulp to 27

#3 Updated by bmbouter 8 months ago

  • Tags deleted (Pulp 3)

#4 Updated by bmbouter 7 months ago

  • Tags Plugin Template added

#5 Updated by bmbouter 7 months ago

  • Project changed from 27 to Pulp

The plugin template Redmine project is being consolidated into the Pulp Redmine project so all issues are being moved over.

Please register to edit this issue

Also available in: Atom PDF