New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open

alfred-SL opened this issue Nov 24, 2022 · 0 comments

alfred-SL commented Nov 24, 2022 •

edited

Loading

For example:

On Jenkins CI run for feature/branch-a, inferred version is 1.0.0-dev.30.
On Jenkins CI run for feature/branch-b, inferred version is 1.0.0-dev.31.
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment