ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Re: Place Ignite TC helper to ASF Ignite supplementary git repo
Date Wed, 18 Jul 2018 22:12:16 GMT
Dmitriy,

Things for clearing the things out. No objections from my side then.

Let's see what other Ignite fellows think on your proposal. Someone might
have a different perspective.

--
Denis

On Wed, Jul 18, 2018 at 1:58 PM Dmitry Pavlov <dpavlov.spb@gmail.com> wrote:

> Hi Denis,
>
> It will made things simple.
>
> 1) For example any comitter will be able to change rules of notification
> and fix the Bot if something goes wrong. Now it is my github repo. ASF repo
> will guarantee that code will be always accessible by community members.
>
> 2) Being a part of ASF repo the Bot will be simple thing that less
> experienced developer can start with. The Bot uses latest AI release as DB
> with persistence enabled, so bot developer became at least Apache Ignite
> user, and as most - new contributor.
>
> If we agree to place this bot to ASF, next step could be asking Infra Team
> to provide 2nd level apache domain, e.g. mtcga.ignite.apache.org for web
> UI. I guess it would be plus if our tool code is available in ASF repo, but
> not in some private git repo.
>
> Sincerely,
> Dmitriy Pavlov
>
> ср, 18 июл. 2018 г. в 23:03, Denis Magda <dmagda@apache.org>:
>
> > Hi Dmitriy,
> >
> > The whole year has passed since this initiative launch, hell, the times
> > passes by :)
> >
> > What would be the benefits of having the tool in the Apache repo? Does it
> > simplify the things for us.
> >
> > --
> > Denis
> >
> > On Wed, Jul 18, 2018 at 3:59 AM Dmitry Pavlov <dpavlov.spb@gmail.com>
> > wrote:
> >
> > > Hi Igniters,
> > >
> > > Almost 1 year has passed since Make Teamcity Green Again was initially
> > > proposed. During this process we managed to get almost successful Run
> > Alls
> > > in master, but currently regressions still occur. We all tried a lot of
> > > things: careful examination of PR tests, continuous monitoring of
> master,
> > > suite responsible contributor, tickets creation and so on.
> > >
> > > According to Igniter's feedback most productive thing was master
> > monitoring
> > > and timely fix of new failures. But contributor’s enthusiasm is limited
> > and
> > > monitoring is not most enjoyable thing, so it's time to automate this
> > > activity. I’ve created MTCGA.Bot which sends emails about new failures
> > and
> > > in addition has a couple of useful features.
> > >
> > > The Bot is being developed only based on your feedback. 30 Ignite
> > > developers already tried it. I'm going to run short
> webinar/presentation
> > at
> > > Mon 23 July and tell more about Bot capabilites, so everyone can make
> an
> > > impression.
> > >
> > > I would like to continue development and I propose to place TC Helper
> > code
> > > to Apache Ignite supplementary repository (same as ignite-release).
> What
> > do
> > > you think about it? Please share your vision till 24 July.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > References:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Make+Teamcity+Green+Again#MakeTeamcityGreenAgain-MTCGABot
> > >
> > > https://github.com/dspavlov/ignite-teamcity-helper
> > >
> >
>

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