[Pulp-dev] Pulp 3 Release Process Questions

Dennis Kliban dkliban at redhat.com
Mon Apr 23 18:03:15 UTC 2018


On Mon, Apr 23, 2018 at 1:45 PM, Jeremy Audet <jaudet at redhat.com> wrote:

> Thanks for answering my questions, all.
>
> > > Let's say pulp_file is being tested. Is both it and pulpcore
> installed from source? Or is pulpcore installed from egg/wheel?
> >
> > Yes, we’re testing against source which also allows us to test against
> different PRs. Often, a pulpcore change will require a pulp_file change or
> vice versa and we just added some functionality recently that actually lets
> us test against PRs too.[1] pulp-smash is also running against source or
> PRs. IMO, testing against source lets us move faster than testing against
> releases. Maybe we can look at switching though once things have stabilized
> after the MVP.
>
> This seems fine in most cases. But when verifying whether a plugin can be
> made into a wheel, this seems like a bad strategy. A brand new wheel should
> work well when installed alongside other wheels from PyPI, and testing
> against from-source installations gives no assurance that this is so.
>
>
That is a great observation. When we automate releasing pulp_file or
another plugin to PyPI using Travis, we will make sure to run tests against
an already published build of pulpcore.


> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180423/ee6d93d2/attachment.htm>


More information about the Pulp-dev mailing list