Details
-
Task
-
Resolution: Done
-
Unknown
-
None
-
None
-
None
Description
The 4.11.0 release failed:
https://parsley.mongodb.com/evergreen/mongo_java_driver_publish_release_publish_releas[…].0_23_10_09_16_46_49/1/task?bookmarks=0,1463&shareLine=1183
|
[2023/10/09 16:54:19.003] Task ':bson:publishArchives' is not up-to-date because:
|
[2023/10/09 16:54:19.003] Task has not declared any outputs despite executing actions.
|
[2023/10/09 16:54:19.003] :bson:publishArchives (Thread[Execution worker for ':',5,main]) completed. Took 0.054 secs.
|
[2023/10/09 16:54:19.104] FAILURE: Build failed with an exception.
|
[2023/10/09 16:54:19.104] * Where:
|
[2023/10/09 16:54:19.104] Script '/data/mci/381684637244d1cd7edfda5342cc2ea5/src/gradle/deploy.gradle' line: 63
|
[2023/10/09 16:54:19.104] * What went wrong:
|
[2023/10/09 16:54:19.104] Execution failed for task ':bson:publishArchives'.
|
[2023/10/09 16:54:19.104] >
|
[2023/10/09 16:54:19.104] Version mismatch:
|
[2023/10/09 16:54:19.104] =================
|
[2023/10/09 16:54:19.104] 4.11.0 != 4.11.0-dirty
|
[2023/10/09 16:54:19.104] The project version does not match the git tag.
|
Unable to reproduce when running what appears to be the same publish process locally, so we released with the locally-produced artifacts.
The task is to figure out why it failed on Evergreen but not locally, as there doesn't appear to be a reason why the local repository on Evergreen would be dirty.
One idea is to include the output of git status in the error message.