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 almost 2 years ago. Updated 3 months ago.

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

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Plugin Template
Sprint:
Quarter:

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 almost 2 years ago

  • Parent task set to #4188

#2 Updated by bmbouter almost 2 years ago

  • Project changed from Pulp to 27

#3 Updated by bmbouter over 1 year ago

  • Tags deleted (Pulp 3)

#4 Updated by bmbouter over 1 year ago

  • Tags Plugin Template added

#5 Updated by bmbouter over 1 year 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.

#6 Updated by daviddavis 3 months ago

  • Status changed from NEW to CLOSED - WONTFIX

Please register to edit this issue

Also available in: Atom PDF