Hi!
We've had some more discussions regarding this topic within the CI
team. Here's a brief summary of the recommendation we agreed upon:
Tests may be written in different ways, but are enabled in a
standard way directly in the package git repository as defined
by the Standard Test Interface.
On 02/25/2018 08:59 PM, Pierre-Yves Chibon wrote:
On Sun, Feb 25, 2018 at 12:12:33PM +, Zbigniew Jędrzejewski-Szmek wrote:
On Thu, Feb 22, 2018 at 03:50:38PM +0100, Pierre-Yves Chibon wrote:
On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
Hi!
During the last days there
On 03/01/2018 04:00 PM, Petr Šplíchal wrote:
To sum up what I've heard so far from the developer side:
* I would like to enable tests for my component (yes, I want)
* I will take care of them (really, I see the benefit in CI)
* I want to easily collaborate on tests with qe (direct commits)
* I
>> To sum up what I've heard so far from the developer side:
>>
>> * I would like to enable tests for my component (yes, I want)
>> * I will take care of them (really, I see the benefit in CI)
>> * I want to easily collaborate on tests with qe (direct commits)
>> * I don't want to give qe commit
On Thu, Mar 01, 2018 at 02:44:37PM +0100, Petr Šplíchal wrote:
> > > > My worries are basically that this mechanism is hiding the
> > > > tests from the package maintainers. It splits the concerns
> > > > between people maintaining the artifacts and people
> > > > maintaining the tests, which is
> > > My worries are basically that this mechanism is hiding the
> > > tests from the package maintainers. It splits the concerns
> > > between people maintaining the artifacts and people
> > > maintaining the tests, which is exactly what the original
> > > plan to bring CI was *not* about.
> >
>
On Sun, Feb 25, 2018 at 12:12:33PM +, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Feb 22, 2018 at 03:50:38PM +0100, Pierre-Yves Chibon wrote:
> > On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
> > > Hi!
> > >
> > > During the last days there have been concerns raised
On Thu, Feb 22, 2018 at 03:50:38PM +0100, Pierre-Yves Chibon wrote:
> On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
> > Hi!
> >
> > During the last days there have been concerns raised regarding
> > what is an appropriate content for the tests namespace. [1] My
> > original idea
On Fri, Feb 23, 2018 at 10:33:57AM +0100, Pavel Raiskup wrote:
> On Thursday, February 22, 2018 3:50:38 PM CET Pierre-Yves Chibon wrote:
> > On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
> > > When, for a particular package, it is the most efficient way to
> > > maintain tests in
On Fri, Feb 23, 2018 at 10:19:35AM +0100, Petr Šplíchal wrote:
> On 22 February 2018 at 15:50, Pierre-Yves Chibon wrote:
> > On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
> >> Hi!
> >>
> >> During the last days there have been concerns raised regarding
> >>
On Thursday, February 22, 2018 3:50:38 PM CET Pierre-Yves Chibon wrote:
> On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
> > When, for a particular package, it is the most efficient way to
> > maintain tests in a separate repo why should we discourage from
> > this approach? There
On 22 February 2018 at 15:50, Pierre-Yves Chibon wrote:
> On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
>> Hi!
>>
>> During the last days there have been concerns raised regarding
>> what is an appropriate content for the tests namespace. [1] My
>> original
On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote:
> Hi!
>
> During the last days there have been concerns raised regarding
> what is an appropriate content for the tests namespace. [1] My
> original idea was to enable sharing tests even across branches of
> the same component, not
On Thu, 2018-02-15 at 13:11 +0100, Petr Šplíchal wrote:
>
> > The question 'who decides which tests block which packages' is
> > left a bit up in the air, but in fact no more so than it already
> > was for package-specific tests...
>
> Right. Do we want to change this? Specify this more
On 14 February 2018 at 18:18, Adam Williamson
wrote:
> On Wed, 2018-02-14 at 17:28 +0100, Petr Šplíchal wrote:
>> Hi!
>>
>> During the last days there have been concerns raised regarding
>> what is an appropriate content for the tests namespace. [1] My
>> original idea
On Wed, 2018-02-14 at 17:28 +0100, Petr Šplíchal wrote:
> Hi!
>
> During the last days there have been concerns raised regarding
> what is an appropriate content for the tests namespace. [1] My
> original idea was to enable sharing tests even across branches of
> the same component, not only for
On 02/14/2018 05:28 PM, Petr Šplíchal wrote:
Hi!
During the last days there have been concerns raised regarding
what is an appropriate content for the tests namespace. [1] My
original idea was to enable sharing tests even across branches of
the same component, not only for tests to be used by
Hi!
During the last days there have been concerns raised regarding
what is an appropriate content for the tests namespace. [1] My
original idea was to enable sharing tests even across branches of
the same component, not only for tests to be used by completely
different packages. The initial
18 matches
Mail list logo