Pulp

Thank you for filing this. The hard part I think is generating the fixtures. Here's a link to the list of dependencies:

https://github.com/pulp/pulp-fixtures#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.

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):
https://github.com/pulp/pulp-operator/blob/master/.travis.yml#L28
https://github.com/pulp/pulp-operator/blob/master/.travis/quay-push.sh

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.

@mikedep333,

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[0] project?

[0] https://github.com/pulp/pulp-fixtures

daviddavis wrote:

@mikedep333,

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[0] project?

[0] https://github.com/pulp/pulp-fixtures

Yes, after reviewing the Dockerfile (which only references files in that repo), I agree.

I can advise on making .travis.yml and other changes.