nebula-release-plugin icon indicating copy to clipboard operation
nebula-release-plugin copied to clipboard

Published 20 hours ago • verified publisher icon nebula-plugins

Question: How does nebula-release-plugin tracks version accross different feature branch?

Open alfred-SL opened this issue 2 years ago • 0 comments

For example:

  1. On Jenkins CI run for feature/branch-a, inferred version is 1.0.0-dev.30.
  2. On Jenkins CI run for feature/branch-b, inferred version is 1.0.0-dev.31.
  3. On Jenkins CI run for feature/branch-c, inferred version is 1.0.0-dev.21. (recent run but version inferred is lower than previous builds)

Where is that dev # (30, 31, 21) comes from? Just trying to understand and see if we should rely on the version generated or set our own.

alfred-SL avatar Nov 24 '22 20:11 alfred-SL