Skip to content
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

Open
refack opened this issue Jun 8, 2018 · 7 comments
Open

CI History and tracability #7

refack opened this issue Jun 8, 2018 · 7 comments

Comments

@refack
Copy link

refack commented Jun 8, 2018

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)

image

ATM Jenkins purges build logs quite often, and GitHub checklist at the bottom of the thread disappears when the PR is closed/merged.

@joyeecheung
Copy link
Member

Is that something we can fix in Jenkins or with GitHub API?

I tend to use ncu-ci --copy to summarize the failures of CI and post them on the thread now, that also works, just takes a bit more manual effort.

@refack
Copy link
Author

refack commented Jun 8, 2018

Is that something we can fix in Jenkins or with GitHub API?

  1. The new checks API allows us to post more information to the PR
  2. We need to either do that in Jenkins, or at least keep more logs.

@richardlau
Copy link
Member

Checks API would seem to be a nice long term solution, but right now I think it is still limited to GitHub Apps.

@mhdawson
Copy link
Member

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.

@joaocgreis
Copy link
Member

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.

@refack
Copy link
Author

refack commented Jun 20, 2018

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 tap2junit and/or a JUnit reporter). I'll prioritize that so we can eliminate the use on the Jenkins TAP plugin.

@joyeecheung
Copy link
Member

joyeecheung commented Jun 20, 2018

In addition we could use ncu-ci walk or part of the code to store the relevant bits periodically. It can generate a JSON that contains all the failures (including bulid failures) in the last 100 runs it parses in a JSON like this, which is not too big because it only store the context of the failures instead of all the logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants