Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
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
- is duplicated by
-
JENKINS-5216 Git plugin should fail build when fetch fails
-
- Closed
-
- is related to
-
JENKINS-4960 Provide a SCMCheckoutStrategy to checkout only once for all matrix entries
-
- Open
-
Activity
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. |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Link |
This issue is duplicated by |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Link | This issue is related to JENKINS-4960 [ JENKINS-4960 ] |
Resolution | Fixed [ 1 ] | |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Workflow | JNJira [ 136999 ] | JNJira + In-Review [ 204325 ] |