Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
From: "Cergey" <cossack5@mail.ru.INVALID>
To: <dev@ignite.apache.org>
References: <0f8801d36a1a$1bc1dc60$53459520$@mail.ru> <0f8b01d36a1a$f9f540d0$eddfc270$@mail.ru> <3B295435-613B-45BC-AFE7-ACE0C59376FC@apache.org> <0fe001d36a75$f528b540$df7a1fc0$@mail.ru> <5FBFFA1C-9C56-4A56-9600-639A6D32D10A@apache.org> <CALUCNEveeH7244Cq0T7ihVkV7rMau4Zde7oKTq=F+8mY=ELJ8w@mail.gmail.com>
In-Reply-To: <CALUCNEveeH7244Cq0T7ihVkV7rMau4Zde7oKTq=F+8mY=ELJ8w@mail.gmail.com>
Subject: RE: ci.ignite.apache: Run all for patch (jira number)
Date: Sat, 2 Dec 2017 03:32:18 +0400
Message-ID: <af1801d36afc$a19696e0$e4c3c4a0$@mail.ru>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Content-language: en-gb
Thread-Index: AQGT2JX+GAcCZtBOLVbSGx3peKddZQGZHDALAj7amE0BtNL0mwJNMF6bAmsvSC6jXBzQ4A==
archived-at: Fri, 01 Dec 2017 23:32:33 -0000

The idea of doing so arose after I uploaded the changed patch second =
time and it didn't appear in teamcity to run against (changes). Should =
automatic build triggering work ? Anyway, I'll go for patch then.

-----Original Message-----
From: Dmitry Pavlov [mailto:dpavlov.spb@gmail.com]=20
Sent: Saturday, December 2, 2017 2:02 AM
To: dev@ignite.apache.org
Subject: Re: ci.ignite.apache: Run all for patch (jira number)

Hi Cergey,

for pull requests I use pull/####/head branch specification in changes =
field (e.g pull/2970/head) and =
https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgnite20Tests_Ru=
nAll run configuration.

Recently we've updated link on GitHub page so new contributors can see =
correct link.

Not sure if `run all for patch` works fine.

Sincerely,
Dmitriy Pavlov

=D0=BF=D1=82, 1 =D0=B4=D0=B5=D0=BA. 2017 =D0=B3. =D0=B2 20:42, Denis =
Magda <dmagda@apache.org>:

> It=E2=80=99s possible but requires you to create a branch and pass its =
name=20
> into
> TeamCity:
>
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#H
> owtoContribute-2.CreateaPatch-file
> <
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#H
> owtoContribute-2.CreateaPatch-file
> >
>
> However, this approach works only for Ignite committers who have=20
> enough permissions for branches creation.
>
> Plus, it=E2=80=99s easier for a reviewer to check the changes via=20
> pull-requests and leave comments there.
>
> =E2=80=94
> Denis
>
> > On Nov 30, 2017, at 11:28 PM, Cergey <cossack5@mail.ru.INVALID> =
wrote:
> >
> > But I want to run the tests against the patch in jira (it is kinda
> easier to make changes in the patch). Is that feasible ?
> >
> > -----Original Message-----
> > From: Denis Magda [mailto:dmagda@apache.org]
> > Sent: Friday, December 1, 2017 4:53 AM
> > To: dev@ignite.apache.org
> > Subject: Re: ci.ignite.apache: Run all for patch (jira number)
> >
> > Cergey,
> >
> > You need to run the tests agains the pull-request. In your case it
> should be this one - pull/2970/merge
> >
> > =E2=80=94
> > Denis
> >
> >> On Nov 30, 2017, at 12:36 PM, Cergey <cossack5@mail.ru.INVALID> =
wrote:
> >>
> >> Probably, I missed something in the patch (
> https://issues.apache.org/jira/browse/IGNITE-6745 ) as builds do not=20
> (and did not) start automatically. What may be wrong ?
> >>
> >> -----Original Message-----
> >> From: Cergey [mailto:cossack5@mail.ru.INVALID]
> >> Sent: Friday, December 1, 2017 12:31 AM
> >> To: dev@ignite.apache.org
> >> Subject: ci.ignite.apache: Run all for patch (jira number)
> >>
> >> Hi, igniters,
> >>
> >> When trying to run "Run all for patch" build with parameter "jira
> number" (existing, e.g. IGNITE-6745 or random), build fails (
> =
https://ci.ignite.apache.org/viewType.html?buildTypeId=3DIgnite20Tests_R
> unAllTestBuilds) with exception: java.net.ConnectException: Connection =

> timed out. Is this functionality not supported or I incorrectly set=20
> the jira number ?
> >>
> >>
> >
> >
>
>