build.timestamp artifacts property should be equal for all artifacts in Build Modules

[gitta-jfrog]

Describe the bug

In case you deploy a build that involves more than one technology, each technology gets its own module.
Following the artifacts published, each module artifact's 'build.timestamp' property will be equal to the start time of the module.

This results in different 'build. timestamp' properties which are not the same as the build started time and cause Artifactory to not match the artifacts to the build info.

Current behavior

Artifacts of different modules get deployed with different 'build.timestamp' property

Reproduction steps

jf rt u abc.txt generic-lcoal/ --build-name cli-test --build-number 21
jf mvn clean install -f pom.xml --build-name cli-test --build-number 21
jf rt bp cli-test 21

Under "Published Modules" the artifacts will not be available (click on the module id and you can see that the repo patch for one technology will be null), although they are uploaded to Artifactory as expected.

see https://jfrog.atlassian.net/browse/RTFACT-30040

Expected behavior

The 'build.timestamp' should be equal for all artifacts in Build Modules

JFrog CLI version

2.50.1

Operating system type and version

Mac

JFrog Artifactory version

7.68.14

JFrog Xray version

NA

[attiasas]

Hi @gitta-jfrog,

Thank you for reporting this issue. After investigating the problem, I found that it is related to Maven and Gradle. We inadvertently used the buildstarted timestamp instead of the general timestamp. You can track the progress of the fix at jfrog/build-info-go#209.

[attiasas]

Hi @gitta-jfrog,

CLI version v2.51.0 has been released, and it includes the fix. Could you please verify that the problem has been resolved and let me know if there are any other issues? Thank you.