ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Artem Shutak <ashu...@gridgain.com>
Subject Re: TeamCity build on master
Date Tue, 11 Aug 2015 17:51:15 GMT
Igniters,

I've done some work with TC: fixed something, filed new jira-s on failed
tests and mute them, fixed configurations. Now it looks better.
Please, keep an eye on it.

Left:
- Ignite Start Nodes - environment issue (I'm working on it).


-- Artem --

On Thu, Aug 6, 2015 at 2:39 PM, Yakov Zhdanov <yzhdanov@gridgain.com> wrote:

> Agree.
>
> --
> Yakov Zhdanov, Director R&D
> *GridGain Systems*
> www.gridgain.com
>
> 2015-08-06 12:07 GMT+03:00 Pavel Tupitsyn <ptupitsyn@gridgain.com>:
>
> > I suggest to fix the wording (current is long and not very English):
> > "There was triggered next test builds for last attached patch-file:" ->
> > "Builds for the latest patch:"
> >
> > Thanks,
> >
> > On Wed, Aug 5, 2015 at 7:31 PM, Artem Shutak <ashutak@gridgain.com>
> wrote:
> >
> > > Auto triggering of TC build by patches was fixed.
> > >
> > > let me know, otherwise.
> > >
> > > -- Artem --
> > >
> > > On Tue, Aug 4, 2015 at 7:22 PM, Artem Shutak <ashutak@gridgain.com>
> > wrote:
> > >
> > > > Why is it large? It contains only information about triggered builds.
> > > >
> > > > But it's possible to have any message that we want. These messages
> > > created
> > > > by our script, not by TC.
> > > >
> > > > -- Artem --
> > > >
> > > > On Tue, Aug 4, 2015 at 6:03 PM, Alexey Kuznetsov <
> > > akuznetsov@gridgain.com>
> > > > wrote:
> > > >
> > > >> It is possible that when TC run builds not to add such large
> comments?
> > > >>
> > > >> On Tue, Aug 4, 2015 at 9:15 PM, Artem Shutak <ashutak@gridgain.com>
> > > >> wrote:
> > > >>
> > > >> > Auto triggering of TC builds for new patches was broken (it's
a
> > reason
> > > >> why
> > > >> > we stopped getting CI builds comments in jira).
> > > >> >
> > > >> > I've filed ticket on it:
> > > >> https://issues.apache.org/jira/browse/IGNITE-1194
> > > >> > .
> > > >> > I've already started working on the issue.
> > > >> >
> > > >> > By the way, there is a possibility to trigger builds for special
> > jira
> > > >> when
> > > >> > auto triggering is broken. Just use
> > > >> >
> > > http://204.14.53.152/viewType.html?buildTypeId=Ignite_RunAllTestBuilds
> > > >> > (with set 'Jira number'). It will add the same CI builds comments
> in
> > > >> jira
> > > >> > issue.
> > > >> >
> > > >> >
> > > >> > -- Artem --
> > > >> >
> > > >> > On Tue, Aug 4, 2015 at 3:54 AM, Dmitriy Setrakyan <
> > > >> dsetrakyan@apache.org>
> > > >> > wrote:
> > > >> >
> > > >> > > By the way, to add to the injury I think we stopped getting
CI
> > build
> > > >> > > comments in Jira tickets. Were those stopped on purpose?
> > > >> > >
> > > >> > > D.
> > > >> > >
> > > >> > > On Mon, Aug 3, 2015 at 5:19 PM, Dmitriy Setrakyan <
> > > >> dsetrakyan@apache.org
> > > >> > >
> > > >> > > wrote:
> > > >> > >
> > > >> > > > Still seeing many failures. Can the responsible parties
please
> > > >> respond
> > > >> > > > suggesting what broke the build?
> > > >> > > >
> > > >> > > > D.
> > > >> > > >
> > > >> > > > On Fri, Jul 31, 2015 at 3:15 PM, Dmitriy Setrakyan
<
> > > >> > > dsetrakyan@apache.org>
> > > >> > > > wrote:
> > > >> > > >
> > > >> > > >> Igniters,
> > > >> > > >>
> > > >> > > >> I am a little disappointed with the current state
of TC on
> > master
> > > >> > > branch:
> > > >> > > >> http://204.14.53.152/
> > > >> > > >>
> > > >> > > >> Most of the builds are RED. Even the Basic test
is failing.
> > > >> > > >>
> > > >> > > >> Are we checking TeamCity before merges? Is TeamCity
build
> > > >> > automatically
> > > >> > > >> triggered for patches?
> > > >> > > >>
> > > >> > > >> D.
> > > >> > > >>
> > > >> > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Alexey Kuznetsov
> > > >> GridGain Systems
> > > >> www.gridgain.com
> > > >>
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > --
> > Pavel Tupitsyn
> > GridGain Systems, Inc.
> > www.gridgain.com
> >
>

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