nebula-plugins / nebula-plugins/nebula-release-plugin
Question: How does nebula-release-plugin tracks version accross different feature branch?
Open
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names Jenkins CI, feature branches, and the generated development versions but no files or tests. Start by locating the plugin's version-inference entry point and tracing how branch or build history produces the dev number. Done means documenting the source of that number and whether generated versions are safe to rely on.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, groovy
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100