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

Extension of "Monitor an external job" jobs.

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      This job-type is nice. It would be even better if:

      1) The e-mail notification could apply for this job-type.

      2) Some of the post-build actions could apply for this job-type (at least "Build
      other projects").

      3) When monitoring an external job, the fact that the job has not run for a
      period of time is often a problem which should be notified. Could we have an
      option to specify a period of time, and functionality so that the e-mail
      notification information from 1) is used to notify that the job has not been
      running lately.

        Attachments

          Issue Links

            Activity

            Hide
            ndcosta Nelson Dcosta added a comment -

            Would be useful to have this functionality in place. Is there a plan to have this fixed ?

            Show
            ndcosta Nelson Dcosta added a comment - Would be useful to have this functionality in place. Is there a plan to have this fixed ?
            Hide
            danielbeck Daniel Beck added a comment -

            FTR the plugin has basically been abandoned, and it never was used much anyway. There's currently only ~4200 external monitor jobs recorded despite having been around for a decade.

            Show
            danielbeck Daniel Beck added a comment - FTR the plugin has basically been abandoned, and it never was used much anyway. There's currently only ~4200 external monitor jobs recorded despite having been around for a decade.
            Hide
            mgancarzdsi Mathew Gancarz added a comment -

            Hi Daniel, I'm curious if this plugin is abandoned, if you are aware of an alternative? I'm using it to monitor long running backup scripts, and running those directly through a Jenkins build by running the bash script through it causes the jenkins server to lock up occasionally as it runs out of memory. (It's a script to tar several tens of millions of files taking up hundreds of GBs, takes about 50+ minutes to run to bash command that runs the tar)

            Show
            mgancarzdsi Mathew Gancarz added a comment - Hi Daniel, I'm curious if this plugin is abandoned, if you are aware of an alternative? I'm using it to monitor long running backup scripts, and running those directly through a Jenkins build by running the bash script through it causes the jenkins server to lock up occasionally as it runs out of memory. (It's a script to tar several tens of millions of files taking up hundreds of GBs, takes about 50+ minutes to run to bash command that runs the tar)
            Hide
            danielbeck Daniel Beck added a comment -

            No alternative I know, just saying there's little to chance of the plugin seeing further development given its sad adoption stats. Despite being bunded for a decade or so, there's only ~4200 jobs total

            I do wonder about the side effects you're describing though. Should probably be isolated, made reproducible, happen on an agent and not Jenkins master (https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Best+Practices) and reported as a bug against core.

            Show
            danielbeck Daniel Beck added a comment - No alternative I know, just saying there's little to chance of the plugin seeing further development given its sad adoption stats. Despite being bunded for a decade or so, there's only ~4200 jobs total I do wonder about the side effects you're describing though. Should probably be isolated, made reproducible, happen on an agent and not Jenkins master ( https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Best+Practices ) and reported as a bug against core.
            Hide
            mgancarzdsi Mathew Gancarz added a comment -

            Even when the job runs without going through Java/jenkins, it still causes the server to become unresponsive at times, so I think it may just be a resource starvation issue rather than anything specific with Jenkins.

            Show
            mgancarzdsi Mathew Gancarz added a comment - Even when the job runs without going through Java/jenkins, it still causes the server to become unresponsive at times, so I think it may just be a resource starvation issue rather than anything specific with Jenkins.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jergan jergan
              Votes:
              16 Vote for this issue
              Watchers:
              14 Start watching this issue

                Dates

                Created:
                Updated: