[
https://issues.apache.org/jira/browse/IGNITE-29137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-29137:
------------------------------------
Fix Version/s: 2.19
> Fix the build timestamp of the version for dev nodes
> ----------------------------------------------------
>
> Key: IGNITE-29137
> URL: https://issues.apache.org/jira/browse/IGNITE-29137
> Project: Ignite
> Issue Type: Task
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
> Fix For: 2.19
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A node started from an IDE currently gets build timestamp 0 in its version
> (see ignite-build-info.properties).
> Scenario:
> 1. 2.19.0-SNAPSHOT binaries are built with Maven. Their build timestamp is
> the timestamp of the last commit in the repository.
> 2. A developer starts a node from the IDE and connects to it with the
> control.sh built in step 1.
> 3. The connection fails because the control.sh version is "greater" than the
> node's. Both versions have the same major.minor.maintenance, so only the
> timestamp decides the comparison, and the IDE node always loses (see
> IgniteComponentFeatureSet#isUpgradableTo) call in
> org.apache.ignite.internal.visor.VisorTaskArgument#readExternal
> Developers don't expect this, and it should be fixed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
