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

polling a nonexistent repository disables the job; add setting to control if this should be done or not

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None

      the subversion plugin disables the job if it is set to poll for a repository (a branches/<versionnr> in my case) that does not exist (yet).

      It would be convenient if this behavior can be disabled, e.g. by a setting 'Do not disable Job if repository does not exist', because now Jobs are disabled and need to be re-enabled somehow when the branch (or tag or project or...) becomes available.
      With this change the Jenkins admin can prepare for projects/branches/... that do not exist yet but will in the near future.

      See also JENKINS-10925: parameter substitution on the SVN url does not seem to work when validating the existence of a repository, which, when polling, results in a disabled job too.

          [JENKINS-10922] polling a nonexistent repository disables the job; add setting to control if this should be done or not

          Julio Morimoto added a comment - - edited

          I'd like to see this option implemented as well.

          We have over 300 projects currently managed by Jenkins. At any point in time, some are disabled, others are enabled. Managing which ones should be enabled/disabled at any time is already a challenge.

          They all rely on subversion polling to trigger builds and deployments to several environments. So, when our network goes under maintenance, there's a chance that the SVN polling is disturbed. Sometimes, SVN servers cannot be reached for some reason. That's not related to Jenkins, but it happens. Most importantly, a lot of times, svn polling errors are temporary.

          In our case, whenever that happens, any number of projects get disabled all at once due to network issues.

          Whatever the reason, we would greatly appreciate if we could control this behavior. We wish polling to continue, even when the URL does not exist or any other polling error occurs.

          Julio Morimoto added a comment - - edited I'd like to see this option implemented as well. We have over 300 projects currently managed by Jenkins. At any point in time, some are disabled, others are enabled. Managing which ones should be enabled/disabled at any time is already a challenge. They all rely on subversion polling to trigger builds and deployments to several environments. So, when our network goes under maintenance, there's a chance that the SVN polling is disturbed. Sometimes, SVN servers cannot be reached for some reason. That's not related to Jenkins, but it happens. Most importantly, a lot of times, svn polling errors are temporary. In our case, whenever that happens, any number of projects get disabled all at once due to network issues. Whatever the reason, we would greatly appreciate if we could control this behavior. We wish polling to continue, even when the URL does not exist or any other polling error occurs.

          jo added a comment -

          Maybe disabling itself makes sense in some environments, to save bandwidth or somesuch. In ordinary cases, you'd want a job to try to run.
          And to run whenever everything required is available and an execution triggered.

          Making this behaviour the norm is irritating, making it the norm and not giving the option to disable that behaviour makes Jenkins look brittle and unreliable.

          So, if there is an option a job shoots itself in the knee, it would be in the interest of being robust and reliable, if that was optional and not the default.

          jo added a comment - Maybe disabling itself makes sense in some environments, to save bandwidth or somesuch. In ordinary cases, you'd want a job to try to run. And to run whenever everything required is available and an execution triggered. Making this behaviour the norm is irritating, making it the norm and not giving the option to disable that behaviour makes Jenkins look brittle and unreliable. So, if there is an option a job shoots itself in the knee, it would be in the interest of being robust and reliable, if that was optional and not the default.

            Unassigned Unassigned
            josbraaksma Jos Braaksma
            Votes:
            7 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: