IGNITE-28863 Fix flaky GridFileDeploymentSelfTest

[wernerdv]

Thank you for submitting the pull request to the Apache Ignite.

In order to streamline the review of the contribution
we ask you to ensure the following steps have been taken:

The Contribution Checklist

• There is a single JIRA ticket related to the pull request.
• The web-link to the pull request is attached to the JIRA ticket.
• The JIRA ticket has the Patch Available state.
• The pull request body describes changes that have been made.
  The description explains WHAT and WHY was made instead of HOW.
• The pull request title is treated as the final commit message.
  The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
• A reviewer has been mentioned through the JIRA comments
  (see the Maintainers list)
• The pull request has been checked by the Teamcity Bot and
  the green visa attached to the JIRA ticket (see tab PR Check at TC.Bot - Instance 1 or TC.Bot - Instance 2)

Notes

• How to Contribute
• Coding abbreviation rules
• Coding Guidelines
• Apache Ignite Teamcity Bot

If you need any help, please email dev@ignite.apache.org or ask anу advice on http://asf.slack.com #ignite channel.

[anton-vinogradov]

The approach looks correct to me: the old <touch> + <zip update="yes"> trick relied on timestamp comparison (with zip's 2-second granularity), so the entry replacement could be silently skipped, leaving the jar validly signed — hence the flakiness. Unpack/replace/repack is deterministic, and since GridUriDeploymentJarVerifier goes through JarFile (name-based lookup, digest check on read), the repacked jar reliably fails verification. Also, the <delete file=...> before <zip> is load-bearing — it defeats Ant's up-to-date check, which could otherwise skip the repack.

A few minor points inline (each applies to both the .jar and the .gar sections).

[ignitetcbot]

TCBot Test Analysis

• TeamCity: --> Run :: All Results
• Branch: pull/13330/head
• Base: master
• Tested commit: e524552

Possible Blockers (0)

No blockers found.

New Tests (0)

No new tests found.