last successful build token displaying wrong value from Jenkins build

Products

• Continuous Delivery Director SAAS

Issue/Introduction

The token passed from a build system like Jenkins is not getting propagated correctly to CDD instead it is picking up a random build number i.e. "200", which is not present on the build system.

Environment

CDD version 6.8 (Running as Docker for Windows)

Cause

The CDD container clock and build system clock goes out of synchronization which result in Tokens not getting correctly identified by CDD as in this case new tokens generated by build system are getting recorded with older date-time and hence CDD is choosing token which is most recent in this case 200 from system Database.

Resolution

Once the clock of CDD running on Docker container and the build system is synchronized the tokens started flowing correctly between the build system and CDD.