CI History and tracability
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
With https://github.com/nodejs/node/pull/21059 we can see that Travis has better history retention and the new GitHub "checks API" does not disappear after the PR is closed (both of these should be taken into consideration for when/if we duplicate auto CI with Jenkins)
ATM Jenkins purges build logs quite often, and GitHub checklist at the bottom of the thread disappears when the PR is closed/merged.
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
No files, tests, or entry points are named. Start by reading the linked pull request and comparing the reported Jenkins log purging with Travis and GitHub Checks history retention. Done requires a concrete, agreed approach for preserving CI history after a pull request is closed or merged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100