quarkusio / quarkusio/quarkus-github-bot
Properly catch errors in Build reports
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 30
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
See this build: https://github.com/quarkusio/quarkus/pull/41593
We somehow filter the jobs we consider for displaying but given that, we should probably not display the table if we don't have any failing jobs.
Contributor guide
No contributing guide indexed for this repository
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 with the build-report handling for the build linked from pull request #41593, tracing how jobs are filtered before the report table is displayed. Verify the behavior when filtering leaves no failing jobs; done means the table is omitted in that case while reports with failing jobs still display it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, java
- Domain
- ci-cd, devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100