-
Notifications
You must be signed in to change notification settings - Fork 812
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
Jenkins check should collect some basic metrics #567
Comments
It looks like we're actually already capturing the build duration in |
Sorting by node would be great as well. For example, we only really care about build times on master, and want to filter out feature branch builds. This functionality exists in the Global Build Stats plugin. |
taking it |
@adamjt about the branch builds, are you talking about git branches ? |
@remh Yes, sorry, nodes was a poor choice of words. My use case is that for alerting, the only thing I care about is a significant change in build time on the master branch. It would be very noisy if that alert metric was polluted with failures and long build times from feature branches, which are expected to be fairly unstable early on. |
@remh We got job duration metrics only once, for a handful of builds that happened a long time ago, and now we're seeing this in the logs: ERROR (init.py:454): Check 'jenkins' instance #0 failed#012Traceback (most recent call last):#12 File "/usr/share/datadog/agent/checks/init.py", line 445, in run#012 self.check(instance)#12 File "/usr/share/datadog/agent/checks.d/jenkins.py", line 141, in check#012 if output['result'] == 'SUCCESS':#012KeyError: 'result' |
Hum not sure it's related to this new metric. |
I'm not sure how to tell which build it's failing on, how would I go about that? |
Hi - We also see this error in our infrastructure. Log below.
It appears to be intermittent (as you can see from previous runs captured in the log). |
Including build times (tagged by build name?), a counter on build failures, etc.
The text was updated successfully, but these errors were encountered: