redhat-developer / redhat-developer/quarkus-ls
Fail when the tests fail in the Jenkins pipeline
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 50
- Forks
- 18
- Avg merge
- 22h 11m
- Merged PRs (30d)
- 3
Description
We ignore test failures in the Jenkinsfile:
https://github.com/redhat-developer/quarkus-ls/blob/master/Jenkinsfile#L34
Resolve the test failures, then remove the parameter to ignore test failures.
The test failures are likely related to the Jenkinsfile or the testing environment, since the tests pass locally and in GitHub Actions.
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 at Jenkinsfile line 34 and compare the Jenkins test behavior with the locally passing tests and GitHub Actions results. Investigate the Jenkinsfile or testing environment as indicated, resolve the Jenkins test failures, then remove the parameter that ignores them and verify the pipeline fails when tests fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100