I have grown used to always running the fixtures container locally in my pulplift boxes using the pfixtures command (essential when working on new fixtures).
This command could be made a bit more flexible (right now it always runs in the foreground and always uses the latest container image from quay.io), but those would be trivial changes. As a result, I personally have no problems with retiring the fixtures on fedorapeople.org completely. The disadvantage of the approach is that it requires either downloading the (pretty large) fixtures container from quay.io, or building it locally. Quirin (quba42) ________________________________ From: pulp-dev-boun...@redhat.com <pulp-dev-boun...@redhat.com> on behalf of David Davis <davidda...@redhat.com> Sent: 28 April 2020 22:19:23 To: Pulp-dev <pulp-dev@redhat.com> Subject: [Pulp-dev] fedorapeople.org fixtures Our Jenkins jobs for Pulp 2 are disabled and that also includes the job that builds the fixtures and publishes them to fedorapeople.org<http://fedorapeople.org>[0]. With the new pulp-fixtures container[1], it's less essential that we have fixtures published somewhere. I think the two options we have are to either retire the fedorapeople.org<http://fedorapeople.org> fixtures and remove them, or to move where the job runs and possibly the place where they are hosted. Thoughts? [0] https://repos.fedorapeople.org/pulp/pulp/fixtures/ [1] https://quay.io/repository/pulp/pulp-fixtures David
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
