[Pulp-dev] Pull Request builder job changes for plugins
bbouters at redhat.com
Fri Jun 2 21:06:59 UTC 2017
That is a good point, and one we are giving some thought to through convo
on #pulp-dev and the issue . The case of a plugin needing an unreleased
change from core would fail with this change. It's a tradeoff though
because if we go with nightlies as the version of core that is used,
whenever the nightlies break, the unittest PR runners also will, which has
been a reliability issue with the plugin unittest runner for a while.
I wrote some on the issue about it, but I see the 'plugin needs unreleased
code from core' as a special case, not a normal case. It used to be common,
but it's getting less common, which is good, because contributing to a
plugin should not involve changes to the core as the norm. It will happen
from time to time, so we can handle the special case, specially by running
the unittests locally with the necessary unreleased version of platform and
posting the results as evidence that its safe to merge.
On Fri, Jun 2, 2017 at 4:43 PM, Michael Hrivnak <mhrivnak at redhat.com> wrote:
> What about cases where a plugin wants to use something that's new in the
> unreleased core? The master branch of a plugin will usually be released
> with the master branch of the core in the next 2.y release for example.
> That seems like a normal scenario; is it facilitated somehow with this
> testing change?
> On Fri, Jun 2, 2017 at 4:33 PM, Dennis Kliban <dkliban at redhat.com> wrote:
>> In an effort to resolve issue 2751, I updated the PR builder job for
>> plugins. Each PR for a plugin will now be tested against the latest stable
>> release of the core found here. This will ensure that the plugin is
>> maintaining compatibility with the latest stable core and that we are only
>> testing one change at a time.
>>  https://pulp.plan.io/issues/2751
>>  https://repos.fedorapeople.org/pulp/pulp/stable/latest/
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
> Michael Hrivnak
> Principal Software Engineer, RHCE
> Red Hat
> Pulp-dev mailing list
> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev