Enable inline Jenkins build status on PRs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 606
- Forks
- 157
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 3
Description
Opening this issue continuing a discussion ignited over in https://github.com/nodejs/github-bot/issues/82.
Before I start fiddling around with getting Jenkins to report build statuses to the github-bot, I want to confirm which build we should do this on? I'm assuming citgm-continuous-integration or citgm-smoker?
Would you agree that we can start off by setting up Jenkins to report build status to a PR specified when starting a build, like we do in nodejs/node, or do you have something else in mind?
/cc @gibfahn @gdams
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
Review the linked github-bot discussion and the citgm-continuous-integration and citgm-smoker Jenkins jobs first. Compare the proposed PR-specific reporting approach with nodejs/node, then confirm which build should report status and what the intended integration should be. Done means the selected Jenkins build reports its status inline on the specified pull request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100