-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI History and tracability #7
Comments
Is that something we can fix in Jenkins or with GitHub API? I tend to use |
|
Checks API would seem to be a nice long term solution, but right now I think it is still limited to GitHub Apps. |
The Jenkins history is purged relatively quickly due to the storage that was consumed by each of the builds. @jbergstroem might have more specific information. |
IIRC having a bigger Jenkins history is blocked on nodejs/build#453 . History is so limited because when opening a job Jenkins parses the output of all runs and this is slow with TAP. |
That is good news, since I'm slowly migrating the jobs to JUnit (with either |
In addition we could use |
With nodejs/node#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.
The text was updated successfully, but these errors were encountered: