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

Errors fetching from remote repos don't fail the build

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • git-plugin
    • None
    • Ubunbu Karmic

    Description

      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.

      Attachments

        Issue Links

          Activity

            ieure ieure created issue -
            ieure ieure made changes -
            Field Original Value New Value
            Description 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.
            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.
            abayer Andrew Bayer made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]
            abayer Andrew Bayer made changes -
            Link This issue is duplicated by JENKINS-5216 [ JENKINS-5216 ]
            eguess74 eguess74 made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]
            garen Garen Parham made changes -
            Link This issue is related to JENKINS-4960 [ JENKINS-4960 ]
            ndeloof Nicolas De Loof made changes -
            Resolution Fixed [ 1 ]
            Status Reopened [ 4 ] Resolved [ 5 ]
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 136999 ] JNJira + In-Review [ 204325 ]

            People

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

              Dates

                Created:
                Updated:
                Resolved: