redhat-developer / redhat-developer/quarkus-ls
Jenkinsfile never deploys OSGi bundles to stable
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 50
- Forks
- 18
- Avg merge
- 22h 11m
- Merged PRs (30d)
- 3
Description
This is dead code:
https://github.com/redhat-developer/quarkus-ls/blob/master/Jenkinsfile#L36
Since we never remove the -SNAPSHOT suffix from the version in the pom, since we want to generate qualifiers for all the OSGi bundles.
Instead of using the pom version to determine if the build is stable, use the VERSION parameter, since it is used to signal a release in the previous step in the build.
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
Start in Jenkinsfile at line 36 and inspect how the POM version determines whether OSGi bundles deploy to stable. Use the VERSION parameter described in the issue instead, then verify that release builds deploy to stable while non-release builds do not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100