Project

Profile

Help

Actions
Send by e-mail Copy link

Story #4200

closed

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

As a Python user, I have containers

Added by bmbouter about 6 years ago. Updated almost 4 years ago.

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

0%

Estimated time:
Platform Release:
Target Release - Python:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

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.

Actions
Copy link
 #1

Updated by bmbouter about 6 years ago

  • Parent issue set to #4188
Actions
Copy link
 #2

Updated by bmbouter over 5 years ago

  • Tags deleted (Pulp 3)
Actions
Copy link
 #3

Updated by gerrod almost 4 years ago

  • Status changed from NEW to CLOSED - CURRENTRELEASE

We have the one for all container witch contains pulp_python. If users require a separate container with just pulp_python they can file a new request at https://github.com/pulp/pulp_python/issues/new.

Actions
Send by e-mail Copy link

Also available in: Atom PDF