RE: ci.ignite.apache: Run all for patch (jira number)
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@gmail.com] 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=Ignite20Tests_RunAll 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 пт, 1 дек. 2017 г. в 20:42, Denis Magda <dma...@apache.org>: > It’s possible but requires you to create a branch and pass its name > 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 > enough permissions for branches creation. > > Plus, it’s easier for a reviewer to check the changes via > pull-requests and leave comments there. > > — > Denis > > > On Nov 30, 2017, at 11:28 PM, Cergey <cossa...@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:dma...@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 > > > > — > > Denis > > > >> On Nov 30, 2017, at 12:36 PM, Cergey <cossa...@mail.ru.INVALID> wrote: > >> > >> Probably, I missed something in the patch ( > https://issues.apache.org/jira/browse/IGNITE-6745 ) as builds do not > (and did not) start automatically. What may be wrong ? > >> > >> -Original Message- > >> From: Cergey [mailto:cossa...@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=Ignite20Tests_R > unAllTestBuilds) with exception: java.net.ConnectException: Connection > timed out. Is this functionality not supported or I incorrectly set > the jira number ? > >> > >> > > > > > >
RE: ci.ignite.apache: Run all for patch (jira number)
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:dma...@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 — Denis > On Nov 30, 2017, at 12:36 PM, Cergey <cossa...@mail.ru.INVALID> wrote: > > Probably, I missed something in the patch > (https://issues.apache.org/jira/browse/IGNITE-6745 ) as builds do not (and > did not) start automatically. What may be wrong ? > > -Original Message- > From: Cergey [mailto:cossa...@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=Ignite20Tests_RunAllTestBuilds) > with exception: java.net.ConnectException: Connection timed out. Is this > functionality not supported or I incorrectly set the jira number ? > >
RE: ci.ignite.apache: Run all for patch (jira number)
Probably, I missed something in the patch (https://issues.apache.org/jira/browse/IGNITE-6745 ) as builds do not (and did not) start automatically. What may be wrong ? -Original Message- From: Cergey [mailto:cossa...@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=Ignite20Tests_RunAllTestBuilds) with exception: java.net.ConnectException: Connection timed out. Is this functionality not supported or I incorrectly set the jira number ?
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=Ignite20Tests_RunAllTestBuilds) with exception: java.net.ConnectException: Connection timed out. Is this functionality not supported or I incorrectly set the jira number ?
RE: Contributor permissions
Thanks. -Original Message- From: Denis Magda [mailto:dma...@apache.org] Sent: Thursday, November 23, 2017 4:30 AM To: dev@ignite.apache.org Subject: Re: Contributor permissions Please try to assign the ticket now and let me know if you still have issues with JIRA. — Denis > On Nov 22, 2017, at 3:38 PM, Cergey <cossa...@mail.ru.INVALID> wrote: > > My username is cossack5. > I have not noticed any change (still can't assign tickets to myself) since I > asked before. Maybe I need to do something on my part ? > > -Original Message- > From: Denis Magda [mailto:dma...@apache.org] > Sent: Thursday, November 23, 2017 1:50 AM > To: dev@ignite.apache.org > Subject: Re: Contributor permissions > > What’s your JIRA id? > > I believe you were added to JIRA’s contributor list before. > > — > Denis > >> On Nov 22, 2017, at 12:22 PM, Cergey <cossa...@mail.ru.INVALID> wrote: >> >> Please, can I be given contributor permissions ? >> >> >> >> Regards, >> >> Cergey Chaulin >> >> >> > >
RE: Contributor permissions
My username is cossack5. I have not noticed any change (still can't assign tickets to myself) since I asked before. Maybe I need to do something on my part ? -Original Message- From: Denis Magda [mailto:dma...@apache.org] Sent: Thursday, November 23, 2017 1:50 AM To: dev@ignite.apache.org Subject: Re: Contributor permissions What’s your JIRA id? I believe you were added to JIRA’s contributor list before. — Denis > On Nov 22, 2017, at 12:22 PM, Cergey <cossa...@mail.ru.INVALID> wrote: > > Please, can I be given contributor permissions ? > > > > Regards, > > Cergey Chaulin > > >
Contributor permissions
Please, can I be given contributor permissions ? Regards, Cergey Chaulin
RE: IGNITE-6745. Status
My username is cossack5. Please grant me contributor permissions. As for java 7 version, until moment it is discontinued, all the code should be java7-compatible ? -Original Message- From: Denis Magda [mailto:dma...@apache.org] Sent: Tuesday, November 21, 2017 3:15 AM To: dev@ignite.apache.org Subject: Re: IGNITE-6745. Status Cergey, What’s you JIRA account? You need to be among Ignite contributors in JIRA to assign tickets on yourself. As for Java 7, yes, we had that discussion many times. Hopefully it will be discontinued the next year. However, as for Java 8 the community is willing to support it by the end of the year. — Denis > On Nov 20, 2017, at 1:45 PM, Cergey <cossa...@mail.ru.INVALID> wrote: > > Hi, > I can't assign the ticket to myself - seems I have no rights. > Also, I see we still support java 7. Maybe it's time to cease it (especially > when we have java 9 to worry about) ? > > -Original Message- > From: Anton Vinogradov [mailto:avinogra...@gridgain.com] > Sent: Monday, November 20, 2017 2:01 PM > To: dev@ignite.apache.org > Subject: Re: IGNITE-6745. Status > > Cergey, > > Please assign https://issues.apache.org/jira/browse/IGNITE-6745 to yourself > and change status to Patch Available. > Also, before asking review, please check that TeamCity status is ok, > see > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#H > owtoContribute-SubmittingforReview > for details. > > > On Sat, Nov 18, 2017 at 12:25 AM, Denis Magda <dma...@apache.org> wrote: > >> Igniters, >> >> Who is going to take a lead of Java 9 support and can do thorough >> review of all the related changes? Here is a set of the tickets and >> Cergey solved one of them: >> https://issues.apache.org/jira/browse/IGNITE-6728 >> >> — >> Denis >> >>> On Nov 16, 2017, at 3:12 PM, Cergey <cossa...@mail.ru.INVALID> wrote: >>> >>> Hi, igniters >>> >>> >>> >>> Why no one commented on the patch and pull request >>> (https://github.com/apache/ignite/pull/2970) ? What should I do ? >>> >>> >>> >>> Regards, >>> >>> Cergey Chaulin >>> >>> >>> >> >> >
RE: IGNITE-6745. Status
Hi, I can't assign the ticket to myself - seems I have no rights. Also, I see we still support java 7. Maybe it's time to cease it (especially when we have java 9 to worry about) ? -Original Message- From: Anton Vinogradov [mailto:avinogra...@gridgain.com] Sent: Monday, November 20, 2017 2:01 PM To: dev@ignite.apache.org Subject: Re: IGNITE-6745. Status Cergey, Please assign https://issues.apache.org/jira/browse/IGNITE-6745 to yourself and change status to Patch Available. Also, before asking review, please check that TeamCity status is ok, see https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-SubmittingforReview for details. On Sat, Nov 18, 2017 at 12:25 AM, Denis Magda <dma...@apache.org> wrote: > Igniters, > > Who is going to take a lead of Java 9 support and can do thorough > review of all the related changes? Here is a set of the tickets and > Cergey solved one of them: > https://issues.apache.org/jira/browse/IGNITE-6728 > > — > Denis > > > On Nov 16, 2017, at 3:12 PM, Cergey <cossa...@mail.ru.INVALID> wrote: > > > > Hi, igniters > > > > > > > > Why no one commented on the patch and pull request > > (https://github.com/apache/ignite/pull/2970) ? What should I do ? > > > > > > > > Regards, > > > > Cergey Chaulin > > > > > > > >
IGNITE-6745. Status
Hi, igniters Why no one commented on the patch and pull request (https://github.com/apache/ignite/pull/2970) ? What should I do ? Regards, Cergey Chaulin
