Make the option to generate fixtures locally available for all plugins
Currently, only pulpcore and pulp_file have the option to generate fixtures locally.
We want that option to be available for all plugins,
since some plugins have limitation to be generated on travis(due ubuntu), one approach would be container based.
#4 Updated by daviddavis 12 months ago
Thank you for filing this. The hard part I think is generating the fixtures. Here's a link to the list of dependencies:
Definitely the hard ones are going to be the rpm dependencies (createrepo, rpmsign, fedpkg, etc).
I don't see us generating fixtures in Travis without some sort of container-based approach. Either generating the fixtures inside a container or just shipping a container with the fixtures already built.
#5 Updated by firstname.lastname@example.org 12 months ago
Using a travis cronjob, we can write and build a container image from a dockerfile (or use buildah to copy the fixtures as arbitrary files into a container image.) In either case, we can try to base it on an existing nginx image.
Once it's built, we can push like we do for pulp-operator (and will soon do for plugins):
However, when the image is pulled, you'll then have to either run it via Docker and point the pulp containers to it, or try to run it via kubernetes. The former is probably easier.
I can advise on all this.
#7 Updated by daviddavis 11 months ago
- Sprint Candidate changed from No to Yes
I've got a Dockerfile that generates the fixtures and serves them via nginx:
#9 Updated by email@example.com 11 months ago
Any idea where the Dockerfile should live and which project should build/push the pulp-fixtures container? I was thinking maybe we could keep it in the pulp-fixtures project?
Yes, after reviewing the Dockerfile (which only references files in that repo), I agree.
I can advise on making .travis.yml and other changes.
#12 Updated by daviddavis 11 months ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset plugin_template|ffe4229608de70c262ef4ab4024a3e2d352124f8.
Please register to edit this issue