ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Boudnik <...@apache.org>
Subject Re: automatic patch validation on TC
Date Tue, 03 Mar 2015 02:50:54 GMT
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
> 

Mime
View raw message