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

Extension of "Monitor an external job" jobs.

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • Platform: All, OS: All

      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.

          [JENKINS-1392] Extension of "Monitor an external job" jobs.

          kutzi added a comment -

          Any news on this one?

          (moving to 'core' component as it IMO belong there)

          kutzi added a comment - Any news on this one? (moving to 'core' component as it IMO belong there)

          Scott Morgan added a comment -

          It does not look trivial to get publishers working with Job classes (vs AbstractProject), especially as MailSender uses AbstractBuild (and Jobs create Runs). A simpler approach would be to have ExternalJob (or ViewJob) be a subclass of AbstractProject. These would be projects with only publishers.

          Seeing that AbstractProject is an extension point, I'll start on a plugin.

          Scott Morgan added a comment - It does not look trivial to get publishers working with Job classes (vs AbstractProject), especially as MailSender uses AbstractBuild (and Jobs create Runs). A simpler approach would be to have ExternalJob (or ViewJob) be a subclass of AbstractProject. These would be projects with only publishers. Seeing that AbstractProject is an extension point, I'll start on a plugin.

          Daniel Beck added a comment -

          core likely needs to be extended for a reusable solution.

          Daniel Beck added a comment - core likely needs to be extended for a reusable solution.

          JENKINS-23713 is the latest incarnation of this issue in the context of the workflow plugin.

          Kohsuke Kawaguchi added a comment - JENKINS-23713 is the latest incarnation of this issue in the context of the workflow plugin.

          Scott Morgan added a comment -

          I created a plugin awhile back to solve this problem. https://wiki.jenkins-ci.org/display/JENKINS/Strawboss+Plugin

          I just recently updated it to fix a bug with configuration persistence. However I can't publish emails using the built in Jenkins post build Email Notification. I can send emails using the Email Extension Plugin.

          Any ideas why I can't send emails? Code is here: https://github.com/jenkinsci/strawboss-plugin

          Scott Morgan added a comment - I created a plugin awhile back to solve this problem. https://wiki.jenkins-ci.org/display/JENKINS/Strawboss+Plugin I just recently updated it to fix a bug with configuration persistence. However I can't publish emails using the built in Jenkins post build Email Notification. I can send emails using the Email Extension Plugin. Any ideas why I can't send emails? Code is here: https://github.com/jenkinsci/strawboss-plugin

          Nelson Dcosta added a comment -

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

          Nelson Dcosta added a comment - Would be useful to have this functionality in place. Is there a plan to have this fixed ?

          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.

          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.

          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)

          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)

          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.

          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.

          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.

          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.

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

              Created:
              Updated: