You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The durationMillis field is always set to 0 when publishing a build using the JFrog CLI.
Current behavior
I am attempting to replace the JFrog Jenkins plugin with the JFrog CLI. However, I noticed that the durationMillis field is always set to 0 when we publish any build with the JFrog CLI. Upon inspecting the repository, I observed that the build info JSON created during the build process does not include any mechanism to set the duration of the build. In contrast, when using the Jenkins Artifactory plugin to publish builds, the durationMillis field is correctly populated.
Reproduction steps
No response
Expected behavior
No response
JFrog CLI-Core version
v2.53.1
JFrog CLI version (if applicable)
jf version 2.58.2
Operating system type and version
docker, linux and windows
JFrog Artifactory version
No response
JFrog Xray version
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
The durationMillis field is always set to 0 when publishing a build using the JFrog CLI.
Current behavior
I am attempting to replace the JFrog Jenkins plugin with the JFrog CLI. However, I noticed that the durationMillis field is always set to 0 when we publish any build with the JFrog CLI. Upon inspecting the repository, I observed that the build info JSON created during the build process does not include any mechanism to set the duration of the build. In contrast, when using the Jenkins Artifactory plugin to publish builds, the durationMillis field is correctly populated.
Reproduction steps
No response
Expected behavior
No response
JFrog CLI-Core version
v2.53.1
JFrog CLI version (if applicable)
jf version 2.58.2
Operating system type and version
docker, linux and windows
JFrog Artifactory version
No response
JFrog Xray version
No response
The text was updated successfully, but these errors were encountered: