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

          Jos Braaksma created issue -
          Jos Braaksma made changes -
          Description Original: 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.
          New: 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.
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 141131 ] New: JNJira + In-Review [ 175423 ]

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

              Created:
              Updated: