[
https://issues.apache.org/jira/browse/IGNITE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14356139#comment-14356139
]
Konstantin Boudnik commented on IGNITE-456:
-------------------------------------------
The code to apply a patch to the local git repo looks like this:
{code}
def patchFile = new File("${jira}.patch")
patchFile << new URL("$ATTACHMENT_URL/$attachementID/").text
checkprocess "git clone --depth 1 $GIT_REPO".execute()
checkprocess "git checkout -b sprint-2 origin/sprint-2".execute(null, new
File('incubator-ignite'))
checkprocess "git am ../${patchFile.name}".execute(null, new
File('incubator-ignite'))
patchFile.delete()
{code}
where {{attachmentID}} will calculated as a part of the provided
patch-checking functionality
> Public TC test builds need to accept two optional parameters
> ------------------------------------------------------------
>
> 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
> Fix For: sprint-2
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
