Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-23933

Expose build successful/unstable/failed metrics

    XMLWordPrintable

Details

    Description

      We are running a couple of Jenkins masters. We have run into problems because nodes are not able to access vital systems like our internal Maven repository or our SCM, sometimes because the hosts were down or because of new VLAN settings or firewalls between nodes or even because of configuration changes.

      In these cases the number of failing builds is increasing immediately. It would be nice if the metrics plugin could provide metrics of successful, unstable and failed builds, so we can react more promptly.

      Attachments

        Activity

          mfriedenhagen Mirko Friedenhagen added a comment - Created PR at https://github.com/jenkinsci/metrics-plugin/pull/3

          Just as a note:

          • We have used this for a week together with the metrics-graphite plugin and push data to InfluxDB, which has a graphite adapter.
          • Visualisation is done with Grafana.
          mfriedenhagen Mirko Friedenhagen added a comment - Just as a note: We have used this for a week together with the metrics-graphite plugin and push data to InfluxDB , which has a graphite adapter. Visualisation is done with Grafana .

          Any feedback?

          mfriedenhagen Mirko Friedenhagen added a comment - Any feedback?
          danielbeck Daniel Beck added a comment -

          Jira is not a good site to solicit feedback.

          Since you seem to be getting ignored by the plugin owner(s), you could request commit access and merge it as described here:
          https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories

          Another option would be to ask for feedback on jenkinsci-dev, but that would be unusual – mostly if you're really unsure about your changes. If a plugin developer is in #jenkins on Freenode, asking directly there would also be an option.

          danielbeck Daniel Beck added a comment - Jira is not a good site to solicit feedback. Since you seem to be getting ignored by the plugin owner(s), you could request commit access and merge it as described here: https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories Another option would be to ask for feedback on jenkinsci-dev, but that would be unusual – mostly if you're really unsure about your changes. If a plugin developer is in #jenkins on Freenode, asking directly there would also be an option.

          Code changed in jenkins
          User: Mirko Friedenhagen
          Path:
          src/main/java/jenkins/metrics/impl/JenkinsMetricProviderImpl.java
          http://jenkins-ci.org/commit/metrics-plugin/e40935251265732178ce1f605a481cec8d038a41
          Log:
          JENKINS-23933: Expose build successful/unstable/failed metrics.

          We are running a couple of Jenkins masters. We have run into problems because nodes are not able to access vital systems like our internal Maven repository or our SCM, sometimes because the hosts were down or because of new VLAN settings or firewalls between nodes or even because of configuration changes.
          In these cases the number of failing builds is increasing immediately. It would be nice if the metrics plugin could provide metrics of successful, unstable and failed builds, so we can react more promptly.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Mirko Friedenhagen Path: src/main/java/jenkins/metrics/impl/JenkinsMetricProviderImpl.java http://jenkins-ci.org/commit/metrics-plugin/e40935251265732178ce1f605a481cec8d038a41 Log: JENKINS-23933 : Expose build successful/unstable/failed metrics. We are running a couple of Jenkins masters. We have run into problems because nodes are not able to access vital systems like our internal Maven repository or our SCM, sometimes because the hosts were down or because of new VLAN settings or firewalls between nodes or even because of configuration changes. In these cases the number of failing builds is increasing immediately. It would be nice if the metrics plugin could provide metrics of successful, unstable and failed builds, so we can react more promptly.

          Code changed in jenkins
          User: Stephen Connolly
          Path:
          src/main/java/jenkins/metrics/impl/JenkinsMetricProviderImpl.java
          http://jenkins-ci.org/commit/metrics-plugin/264a210d6e4b6575ebf0f37f00385ac71315cfd2
          Log:
          Merge pull request #3 from mfriedenhagen/JENKINS-23933

          JENKINS-23933: Expose build successful/unstable/failed metrics.

          Compare: https://github.com/jenkinsci/metrics-plugin/compare/79d151a18216...264a210d6e4b

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Stephen Connolly Path: src/main/java/jenkins/metrics/impl/JenkinsMetricProviderImpl.java http://jenkins-ci.org/commit/metrics-plugin/264a210d6e4b6575ebf0f37f00385ac71315cfd2 Log: Merge pull request #3 from mfriedenhagen/ JENKINS-23933 JENKINS-23933 : Expose build successful/unstable/failed metrics. Compare: https://github.com/jenkinsci/metrics-plugin/compare/79d151a18216...264a210d6e4b

          PR was merged

          mfriedenhagen Mirko Friedenhagen added a comment - PR was merged

          People

            Unassigned Unassigned
            mfriedenhagen Mirko Friedenhagen
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: