Use latest release +1 as new version instead of using Jenkins build number
Description
Environment
None
Activity
Show:

Ding-Yi Chen 24 January 2018 at 00:46
We decide to turn off the old jenkins , thus avoid the confusion and collision.

Sean Flanigan 17 January 2018 at 03:22
I think the current versioning scheme is okay. Using oldVersion+1 won't fix anything if two jobs are running at once. We should just turn off one of the jobs so that they aren't fighting.
Won't Fix
Details
Details
Assignee

Reporter

Sprint
None
Priority

More fields
Time tracking
More fields
Time trackingCreated 17 January 2018 at 01:58
Updated 24 January 2018 at 00:46
Resolved 24 January 2018 at 00:46
Current, Jenkins build number is used in last part of version.
This was helpful to locate the build tasks in Jenkins.
However, when we have 2 Jenkins due to Jenkins 2.6 migration, each Jenkins has different build Id,
thus cause confusion and some tasks failed because the build Id was used by other Jenkins.