The maven-merge jobs in ODL is NOT using the maven-merge from globla-jjb, is using it's legacy merge jobs. We deployed maven-merge a year ago and the community noticed some issues that was caused SNAPSHOT timestamp off by 1 errors so we backed out of the deployment. Eventually we learned that it's fixed in Maven 3.5.2 so we can switch the jobs back at some point but now is not a good time considering the imminant release.