You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Konstantin Boudnik <co...@apache.org> on 2015/03/03 03:50:54 UTC
Re: automatic patch validation on TC
Any comments, feedback? If not, I will start digging myself, but it might take
an extra time.
On Sat, Feb 28, 2015 at 05:22AM, Konstantin Boudnik wrote:
> Y'all
>
> I have put together an initial version of the TC job that pulls in JIRAs in PA
> state and find the latest attachment by date. It also creates and artifact
> where all earlier processed attachments are listed to avoid duplicated
> test runs. The job is here
> http://204.14.53.152/viewType.html?buildTypeId=Ignite_PatchValidation_Main
>
> Now, I need some advice from TC experts, as I have no experience with it,
> really. The issue I have as this (perhaps, coming from my ignorance about TC):
> 1. it seems that TC builds can be triggered by creating a special remote
> branch in git. That would require a job to do pushed to the git, which I
> am no fan of...
> 2. there might be a way to use some sort of meta-runner that can fetch the
> repo, create a branch using provided patch, and then trigger the test-run.
> I have no idea how to do it.
> 3. Some other unknown-unknown functionality, that I am evidently missing?
>
> I would really like someone on this list with TC expertise to tell me what's
> the preferred way of performing such workflow? E.g. in Jenkins I can trigger a
> remote job with a parameter (JIRA #), which then will download the latest
> attachment from it (7 lines of Groovy), apply it to the fresh repo clone and
> run the tests. How we can do something like that in TC? Looking for the
> guidance and help from this list.
>
> --
> Thanks in advance. Regards,
> Cos
>
Re: automatic patch validation on TC
Posted by Konstantin Boudnik <co...@apache.org>.
Ok, so similar to the workflow in Jenkins. Ok, I will try to do it. For the
safety sake, I will create a new test project from the template, so I don't
ruin anything.
Thanks Val
Cos
On Mon, Mar 02, 2015 at 07:32PM, Valentin Kulichenko wrote:
> I've never done such configuration myself, but I think this could work:
>
> - add a parameter that specifies JIRA# to Ignite::Maven template
> - add additional step (Groovy script?) which will download the patch and
> apply it to working directory
>
> The build can be triggered using REST API:
> https://confluence.jetbrains.com/display/TCD8/REST+API#RESTAPI-TriggeringaBuild
>
> --
> Val
>
> On Mon, Mar 2, 2015 at 6:50 PM, Konstantin Boudnik <co...@apache.org> wrote:
>
> > Any comments, feedback? If not, I will start digging myself, but it might
> > take
> > an extra time.
> >
> > On Sat, Feb 28, 2015 at 05:22AM, Konstantin Boudnik wrote:
> > > Y'all
> > >
> > > I have put together an initial version of the TC job that pulls in JIRAs
> > in PA
> > > state and find the latest attachment by date. It also creates and
> > artifact
> > > where all earlier processed attachments are listed to avoid duplicated
> > > test runs. The job is here
> > >
> > http://204.14.53.152/viewType.html?buildTypeId=Ignite_PatchValidation_Main
> > >
> > > Now, I need some advice from TC experts, as I have no experience with it,
> > > really. The issue I have as this (perhaps, coming from my ignorance
> > about TC):
> > > 1. it seems that TC builds can be triggered by creating a special remote
> > > branch in git. That would require a job to do pushed to the git,
> > which I
> > > am no fan of...
> > > 2. there might be a way to use some sort of meta-runner that can fetch
> > the
> > > repo, create a branch using provided patch, and then trigger the
> > test-run.
> > > I have no idea how to do it.
> > > 3. Some other unknown-unknown functionality, that I am evidently
> > missing?
> > >
> > > I would really like someone on this list with TC expertise to tell me
> > what's
> > > the preferred way of performing such workflow? E.g. in Jenkins I can
> > trigger a
> > > remote job with a parameter (JIRA #), which then will download the latest
> > > attachment from it (7 lines of Groovy), apply it to the fresh repo clone
> > and
> > > run the tests. How we can do something like that in TC? Looking for the
> > > guidance and help from this list.
> > >
> > > --
> > > Thanks in advance. Regards,
> > > Cos
> > >
> >
Re: automatic patch validation on TC
Posted by Valentin Kulichenko <va...@gmail.com>.
I've never done such configuration myself, but I think this could work:
- add a parameter that specifies JIRA# to Ignite::Maven template
- add additional step (Groovy script?) which will download the patch and
apply it to working directory
The build can be triggered using REST API:
https://confluence.jetbrains.com/display/TCD8/REST+API#RESTAPI-TriggeringaBuild
--
Val
On Mon, Mar 2, 2015 at 6:50 PM, Konstantin Boudnik <co...@apache.org> wrote:
> Any comments, feedback? If not, I will start digging myself, but it might
> take
> an extra time.
>
> On Sat, Feb 28, 2015 at 05:22AM, Konstantin Boudnik wrote:
> > Y'all
> >
> > I have put together an initial version of the TC job that pulls in JIRAs
> in PA
> > state and find the latest attachment by date. It also creates and
> artifact
> > where all earlier processed attachments are listed to avoid duplicated
> > test runs. The job is here
> >
> http://204.14.53.152/viewType.html?buildTypeId=Ignite_PatchValidation_Main
> >
> > Now, I need some advice from TC experts, as I have no experience with it,
> > really. The issue I have as this (perhaps, coming from my ignorance
> about TC):
> > 1. it seems that TC builds can be triggered by creating a special remote
> > branch in git. That would require a job to do pushed to the git,
> which I
> > am no fan of...
> > 2. there might be a way to use some sort of meta-runner that can fetch
> the
> > repo, create a branch using provided patch, and then trigger the
> test-run.
> > I have no idea how to do it.
> > 3. Some other unknown-unknown functionality, that I am evidently
> missing?
> >
> > I would really like someone on this list with TC expertise to tell me
> what's
> > the preferred way of performing such workflow? E.g. in Jenkins I can
> trigger a
> > remote job with a parameter (JIRA #), which then will download the latest
> > attachment from it (7 lines of Groovy), apply it to the fresh repo clone
> and
> > run the tests. How we can do something like that in TC? Looking for the
> > guidance and help from this list.
> >
> > --
> > Thanks in advance. Regards,
> > Cos
> >
>