[
https://issues.apache.org/jira/browse/IGNITE-23094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17877999#comment-17877999
]
Ignite TC Bot commented on IGNITE-23094:
----------------------------------------
{panel:title=Branch: [pull/11499/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/11499/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=8047637&buildTypeId=IgniteTests24Java8_RunAll]
> Add settings argument to all maven command invoked by compatibility tests
> -------------------------------------------------------------------------
>
> Key: IGNITE-23094
> URL: https://issues.apache.org/jira/browse/IGNITE-23094
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Petrov
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> It is needed to add settings argument to all maven command invoked by
> compatibility tests. So custom Ignite test deployments can override maven
> settings for all commands.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
