Mailing-List: contact issues-help@ignite.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.incubator.apache.org
Date: Thu, 21 May 2015 11:08:01 +0000 (UTC)
From: "Artem Shutak (JIRA)" <jira@apache.org>
To: issues@ignite.incubator.apache.org
Message-ID: <JIRA.12781070.1426042359000.180135.1432206481032@Atlassian.JIRA>
In-Reply-To: <JIRA.12781070.1426042359000@Atlassian.JIRA>
References: <JIRA.12781070.1426042359000@Atlassian.JIRA>
 <JIRA.12781070.1426042359532@arcas>
Subject: [jira] [Updated] (IGNITE-456) [Public TC] Need to complete patch
 validation mechanism.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/IGNITE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Artem Shutak updated IGNITE-456:
--------------------------------
    Attachment: sout_test.patch

> [Public TC] Need to complete patch validation mechanism.
> --------------------------------------------------------
>
>                 Key: IGNITE-456
>                 URL: https://issues.apache.org/jira/browse/IGNITE-456
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: sprint-1
>            Reporter: Konstantin Boudnik
>            Assignee: Artem Shutak
>            Priority: Blocker
>             Fix For: sprint-5
>
>         Attachments: ignite-456-patch-validation-2.txt, ignite-456-patch-validation-2.txt, patch-456-2.file, patch-456.file, sout_test.patch
>
>
> h4. Original task scope: "Public TC test builds need to accept the optional parameter"
> Test builds should be able to accept the following optional parameter:
> - JIRA number
> If the parameter is passed in, then an extra build step needs to be execute to get the latest attachment from the JIRA ticket and {{git am}} it into the local Ignite repo before running the tests.
> Important to notice, the the patch needs to be applied once before running all required tests. At some late point we might add the logic to only run tests in the affected modules, but it could be a bit of a challenge. 
> h4. New scope of task
> TODO:
> - find way to run TC build with paramether from another build - Done
> - configure new task to run all Ignite builds
> - configure task to get all NEW patches from JIRAs and run them on TC
> To check:
> - comment on jira for which builds were started
> - tasks for each patch started once
> Current issues:
> - curl does not work properly on agents


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)