ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergi Vladykin <sergi.vlady...@gmail.com>
Subject Re: TC hell
Date Thu, 27 Aug 2015 13:24:49 GMT
I think we have to switch to manual TC runs, this will solve the problem.
Guest account should not be able to run anything in my view anyways,
it must be allowed only for registered contributors.

Sergi

2015-08-27 12:16 GMT+03:00 Raul Kripalani <raul@evosent.com>:

> I'm not familiar with TC, but I've seen other projects have set it up in a
> way to trigger a build when a committer types a magic comment in the PR
> such as: "TC please build".
>
> Not sure if they're using TC or something else, but it's definitely worth
> investigating.
> On 27 Aug 2015 07:56, "Denis Magda" <dmagda@gridgain.com> wrote:
>
> > Definitely we have to change something here.
> >
> > I would use a manual triggering  granting access through a special
> account
> > available only to contributors and commiters.
> >
> > --
> > Denis
> >
> > On 8/27/2015 9:51 AM, Valentin Kulichenko wrote:
> >
> >> Igniters,
> >>
> >> We currently have >200 builds in TC queue and it will take around 15
> hours
> >> to run everything. This is becoming unusable.
> >>
> >> It seems to me that it got worse after we switched to pull requests,
> >> because builds are triggered each time someone pushes to the branch that
> >> is
> >> tied up with existing PR. I'm sure that not all of these builds are
> really
> >> needed, so I suggest to disable automatic trigger and always start
> builds
> >> manually (we already have 'Run All' configuration in case you need all
> >> suites).
> >>
> >> The only issue - right now manual run is not possible under Guest
> account.
> >> So we will have to either change Guest permissions or add special
> account
> >> for this.
> >>
> >> Thoughts?
> >>
> >> -Val
> >>
> >>
> >
>

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