ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavel Tupitsyn <ptupit...@apache.org>
Subject Re: Change TC trigger from Run All to per-project basis
Date Wed, 21 Feb 2018 07:26:23 GMT
Dmitry, thanks for the explanation, this makes sense.

1) Certainly can be helpful.
2) I would include "Platform .NET Core Linux": does not require win agent,
runs 15 min, covers most functionality.

Pavel

On Wed, Feb 21, 2018 at 12:12 AM, Dmitry Pavlov <dpavlov.spb@gmail.com>
wrote:

> Hi Pavel,
>
> WDYT,
> 1) is it needed to prepare wiki article describing tests and chains we
> have, e.g. describe
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_
> RunBasicTests
> and
> its difference with RunAll; which chain to use in each case?
>
> 2) Which .Net test suite may be applicable to be included into 'run basic
> tests' (requires <30 min to run, no failed test, no flaky test with fail
> rate >1%) ?
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 19 февр. 2018 г. в 0:39, Pavel Tupitsyn <ptupitsyn@apache.org>:
>
> > Igniters,
> >
> > Currently we have a TeamCity trigger only on Run All aggregating project:
> >
> > https://ci.ignite.apache.org/admin/editTriggers.html?id=
> buildType:IgniteTests24Java8_RunAll
> >
> > Each change triggers it's own full run. If new changes are added while
> some
> > builds are queued,
> > these changes are not picked up, and a separate run is scheduled.
> >
> > At this very moment I see over 600 queued builds, all on master branch
> from
> > some trigger.
> > Previously we had a trigger per-project, which seems to be more
> efficient.
> >
> > Thoughts?
> >
> > Pavel
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message