Re: [Pulp-dev] Github Required Checks

I don't think we should make it a hard *physical* block on PR merging. Setting aside the occasional infrastructure issues, we also have some unit tests (in pulp core, at least) that rely on e.g. non-expired certificates, and fixing those once they break would require circumventing the process or

[Pulp-dev] Github Required Checks

A week or two ago on irc, @misa identified that unit tests which run on travis with crane prs had been failing for a long time. These unit tests are run on each PR that is submitted, but broken and ignored. We were interested in finding a better way to ensure that our required checks all must pass

Re: [Pulp-dev] pulp 3 distributor use cases

+1 rename On Fri, Feb 2, 2018 at 10:51 AM, Austin Macdonald wrote: > +1 rename to Exporter. > > On Fri, Feb 2, 2018 at 10:13 AM, Brian Bouterse > wrote: > >> +1 to renaming a Pulp3 'Distributor' to be 'Exporter'. The name of a >> 'Distribution' (when

Re: [Pulp-dev] pulp 3 distributor use cases

+1 rename to Exporter. On Fri, Feb 2, 2018 at 10:13 AM, Brian Bouterse wrote: > +1 to renaming a Pulp3 'Distributor' to be 'Exporter'. The name of a > 'Distribution' (when Pulp serves bits using its webserver) would stay the > same. Currently the names Distributor and

Re: [Pulp-dev] pulp 3 distributor use cases

On Fri, Feb 2, 2018 at 12:38 AM, Eric Helms wrote: > > > On Thu, Feb 1, 2018 at 10:30 AM, Dennis Kliban wrote: > >> Distributors are only used for exporting Publications out of Pulp. >> >> Distributions make Publications available to consume via http(s) at