[ 
https://issues.apache.org/jira/browse/IGNITE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14554083#comment-14554083
 ] 

tc_commenter commented on IGNITE-456:
-------------------------------------

There was triggered next test builds for last attached patch-file:
Ignite AOP - http://204.14.53.152/viewQueued.html?itemId=84099
Ignite AWS - http://204.14.53.152/viewQueued.html?itemId=84100
Ignite Basic - http://204.14.53.152/viewQueued.html?itemId=84095
Ignite Cache - http://204.14.53.152/viewQueued.html?itemId=84102
Ignite Cache 2 - http://204.14.53.152/viewQueued.html?itemId=84103
Ignite Cache 3 - http://204.14.53.152/viewQueued.html?itemId=84104
Ignite Cache 4 - http://204.14.53.152/viewQueued.html?itemId=84105
Ignite Cache Expiry Policy - http://204.14.53.152/viewQueued.html?itemId=84106
Ignite Cache Failover - http://204.14.53.152/viewQueued.html?itemId=84107
Ignite Cache Full API - http://204.14.53.152/viewQueued.html?itemId=84108
Ignite Cache Restarts - http://204.14.53.152/viewQueued.html?itemId=84109
Ignite Cache Tx Recovery - http://204.14.53.152/viewQueued.html?itemId=84110
Ignite Cloud - http://204.14.53.152/viewQueued.html?itemId=84111
Ignite Compute Grid - http://204.14.53.152/viewQueued.html?itemId=84112
Ignite Data Strucutures - http://204.14.53.152/viewQueued.html?itemId=84113
Ignite Examples - http://204.14.53.152/viewQueued.html?itemId=84114
Ignite GCE - http://204.14.53.152/viewQueued.html?itemId=84115
Ignite Geospacial Indexing - http://204.14.53.152/viewQueued.html?itemId=84116
Ignite H2 Indexing - http://204.14.53.152/viewQueued.html?itemId=84117
Ignite Hadoop - http://204.14.53.152/viewQueued.html?itemId=84118
Ignite Hibernate - http://204.14.53.152/viewQueued.html?itemId=84119
Ignite IGFS - http://204.14.53.152/viewQueued.html?itemId=84120
Ignite IGFS Examples - http://204.14.53.152/viewQueued.html?itemId=84121
Ignite IGFS Linux and MacOS - http://204.14.53.152/viewQueued.html?itemId=84122
Ignite Java Client - http://204.14.53.152/viewQueued.html?itemId=84123
Ignite JDBC Driver - http://204.14.53.152/viewQueued.html?itemId=84124
Ignite JTA - http://204.14.53.152/viewQueued.html?itemId=84125
Ignite Logging - http://204.14.53.152/viewQueued.html?itemId=84126
Ignite Logging-Patch - http://204.14.53.152/viewQueued.html?itemId=84127
Ignite Queries - http://204.14.53.152/viewQueued.html?itemId=84128
Ignite Scalar Examples - http://204.14.53.152/viewQueued.html?itemId=84129
Ignite SPI - http://204.14.53.152/viewQueued.html?itemId=84130
Ignite Spring - http://204.14.53.152/viewQueued.html?itemId=84131
Ignite Start Nodes - http://204.14.53.152/viewQueued.html?itemId=84132
Ignite URI Deploy SPI - http://204.14.53.152/viewQueued.html?itemId=84133
Ignite Visor Console - http://204.14.53.152/viewQueued.html?itemId=84134
Ignite WebSessions - http://204.14.53.152/viewQueued.html?itemId=84135
JCache TCK - http://204.14.53.152/viewQueued.html?itemId=84136


> [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
>
>
> 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)

Reply via email to