jenkinsci/jenkins
Jenkins automation server
In plain words
Outside PRs: 4 in 10 merged. First reply usually within 6 h. 4 starter issues are available now. Replies slowed down this month.
Outside PRs merged
37%
54 merged, 93 closed, 30 still open
Higher than 6% of 565 other measured repositories
First human reply
6 h
median of 177 outside PRs, 43 unanswered
Time to merge
Not enough data
54 of 177 outside PRs merged
Outside PRs opened 30 to 120 days ago, so each has had time to be answered. A figure needs at least 5 pull requests, otherwise it reads "Not enough data". How this is calculated · A number looks wrong?
Your first steps here
If you have never contributed to this project, do these in order.
- 1
Read the contributing guide
It says how to set the project up and what the maintainers expect in a pull request.
Open the guide - 2
Take this free issue
[JENKINS-49202] ChangeLogSet.Entry does not expose getComment to get entire commit message
Open issue #22542 - 3
Know where to ask
Questions go to the project's matrix, or on the issue itself. Not in private messages.
Open it - 4
Open a small pull request
Link the issue in it. A first reply here usually takes 6 h; until then, silence is normal.
What happens to an outside pull request
Every pull request opened by someone outside the core team, 30 to 120 days ago.
- Opened by outsiders177100%
- Got a human reply13476%
- Merged5431%
Time to first reply
After 2 days, 63% of outside PRs had a reply from a person. After a week, 69%. Bots do not count.
The last 52 weeks
Slowed down. Median first reply was 3.6 days over the last four weeks (51 PRs) and 5 h over the four before (44 PRs).
Starter issues
Issues labelled for beginners, with their real state. Available means open, unassigned, no linked pull request, nobody has claimed it in the last 14 days, and it was updated in the last 60 days.
- Available
- 4
- Claimed
- 0
- Has a pull request
- 0
- Stale
- 9
When replies arrive
All maintainers counted together. Shown only when at least 3 people replied in the last 90 days, so it never describes one person.
Replies are most likely between 19:00 and 22:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 10 |
| 01:00 | 12 |
| 02:00 | 19 |
| 03:00 | 14 |
| 04:00 | 4 |
| 05:00 | 2 |
| 06:00 | 1 |
| 07:00 | 2 |
| 08:00 | 2 |
| 09:00 | 0 |
| 10:00 | 0 |
| 11:00 | 4 |
| 12:00 | 21 |
| 13:00 | 20 |
| 14:00 | 9 |
| 15:00 | 9 |
| 16:00 | 14 |
| 17:00 | 22 |
| 18:00 | 19 |
| 19:00 | 17 |
| 20:00 | 23 |
| 21:00 | 19 |
| 22:00 | 11 |
| 23:00 | 11 |
How to start
- Contributing guidefound
- Code of conductfound
- Issue templatesnot found
- Dev container for one-step setupnot found
- No CLA or sign-off requirement was found.
Where the project talks
Activity
- Commits, 90 days
- 301
- Releases, 12 months
- 30
- Active maintainers
- 16
- Last push
- 11 Oct 2026
Stack
Badge and feed
Two ways to use these figures outside this page.
For maintainers: a README badge
Shows newcomers how quickly this project answers and how often it merges. Paste the line into your README; the badge updates with the index.
[](https://contributable.vercel.app/repo/jenkinsci/jenkins)[](https://contributable.vercel.app/repo/jenkinsci/jenkins)For contributors: follow new issues
Add the feed to a feed reader (Feedly, Inoreader, Thunderbird) and you hear about new free starter issues here without checking the site.
https://contributable.vercel.app/feed/repo/jenkinsci/jenkinsFor developers: every figure on this page as JSON at /api/v1/repos/jenkinsci/jenkins.
Similar repositories
Same main language (Java), most shared frameworks and topics first, then the faster reply.
Pipeline Graph View adds a visual representation of Jenkins pipelines, showing each stage of a run in a clear and easy-to-follow graph forma
- First reply
