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

Errors fetching from remote repos don't fail the build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • git-plugin
    • None
    • Ubunbu Karmic

      If there is a problem fetching new changes from a remote repo, this doesn't fail the build. Example:

      ERROR: Permission to simplegeo/python-geojson denied to geebus.
fatal: The remote end hung up unexpectedly
ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway

      Despite this, the build proceeds and is considered successful. This is extremely misleading, as it contains no new changes from the only repository it is configured to pull from. While I believe this behavior is nonsensical in the majority of cases, I think that one of two things should be changed:

      1. If every remote repo fails to update, fail.
      OR
      2. Add an option to fail if any remote repo fails to update.

          [JENKINS-6902] Errors fetching from remote repos don't fail the build

          ieure created issue -
          ieure made changes -
          Description Original: If there is a problem fetching new changes from a remote repo, this doesn't fail the build. Example:

          {code}
          ERROR: Permission to simplegeo/python-geojson denied to geebus.
          fatal: The remote end hung up unexpectedly
          ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway
          {code}

          Despite this, the build proceeds and is considered successful. This is extremely misleading, as it contains no new changes from the only repository it is configured to pull from. While I believe this behavior is nonsensical in the majority of cases, I think that one of two things should be changed:

           1. If _every_ remote repo fails to update, fail.
            -OR-
           2. Add an option to fail if _any_ remote repo fails to update.           		New: If there is a problem fetching new changes from a remote repo, this doesn't fail the build. Example:

          {code}
          ERROR: Permission to simplegeo/python-geojson denied to geebus.
          fatal: The remote end hung up unexpectedly
          ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway
          {code}

          Despite this, the build proceeds and is considered successful. This is extremely misleading, as it contains no new changes from the only repository it is configured to pull from. While I believe this behavior is nonsensical in the majority of cases, I think that one of two things should be changed:

           1. If _every_ remote repo fails to update, fail.
            *OR*
           2. Add an option to fail if _any_ remote repo fails to update.
          Andrew Bayer made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Link New: This issue is duplicated by JENKINS-5216 [ JENKINS-5216 ]
          eguess74 made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Garen Parham made changes -
          Link New: This issue is related to JENKINS-4960 [ JENKINS-4960 ]
          Nicolas De Loof made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]
          Mark Waite made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 136999 ] New: JNJira + In-Review [ 204325 ]

            abayer Andrew Bayer
            ieure ieure
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: