Jenkins CI status: Bot should not look for latest commit in PR
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 305
- Forks
- 148
- Avg merge
- 9h 2m
- Merged PRs (30d)
- 3
Description
Right now the bot looks for the latest commit in a PR, but it should refer to the commit that the build was kicked off for.
It seems like there’s a commit field in the Jenkins push event body, so that should be pretty simple to do, I just don’t really know how to test this?
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 by tracing the Jenkins push-event handling and inspect the event body’s commit field alongside how the bot currently finds a PR’s latest commit. Verify that Jenkins status handling uses the commit that triggered the build, and determine how this behavior can be tested from the repository’s existing test setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100