[JIRA] Created: (HUDSON-6902) Errors fetching from remote repos don't fail the build

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (HUDSON-6902) Errors fetching from remote repos don't fail the build

Hudson issues mailing list
Errors fetching from remote repos don't fail the build
------------------------------------------------------

                 Key: HUDSON-6902
                 URL: http://issues.hudson-ci.org/browse/HUDSON-6902
             Project: Hudson
          Issue Type: Bug
          Components: git
    Affects Versions: current
         Environment: Ubunbu Karmic
            Reporter: ieure
            Assignee: abayer
             Fix For: current


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.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (HUDSON-6902) Errors fetching from remote repos don't fail the build

Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ieure updated HUDSON-6902:
--------------------------

    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.

  was:
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.


> Errors fetching from remote repos don't fail the build
> ------------------------------------------------------
>
>                 Key: HUDSON-6902
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6902
>             Project: Hudson
>          Issue Type: Bug
>          Components: git
>    Affects Versions: current
>         Environment: Ubunbu Karmic
>            Reporter: ieure
>            Assignee: abayer
>             Fix For: current
>
>
> 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.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6902) Errors fetching from remote repos don't fail the build

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139815#action_139815 ]

abayer commented on HUDSON-6902:
--------------------------------

I like option #1 - I'm not a particular fan of this behavior either, but I don't want to break anyone depending on the build continuing if one of multiple repos fails, and I don't want to add more configuration options than absolutely necessary.

> Errors fetching from remote repos don't fail the build
> ------------------------------------------------------
>
>                 Key: HUDSON-6902
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6902
>             Project: Hudson
>          Issue Type: Bug
>          Components: git
>    Affects Versions: current
>         Environment: Ubunbu Karmic
>            Reporter: ieure
>            Assignee: abayer
>             Fix For: current
>
>
> 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.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Resolved: (HUDSON-6902) Errors fetching from remote repos don't fail the build

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

     [ http://issues.hudson-ci.org/browse/HUDSON-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

abayer resolved HUDSON-6902.
----------------------------

    Resolution: Fixed

Fixed in latest at github.com/hudson/Hudson-GIT-plugin's master branch - if all fetches fail, the build will be marked as failed.

> Errors fetching from remote repos don't fail the build
> ------------------------------------------------------
>
>                 Key: HUDSON-6902
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6902
>             Project: Hudson
>          Issue Type: Bug
>          Components: git
>    Affects Versions: current
>         Environment: Ubunbu Karmic
>            Reporter: ieure
>            Assignee: abayer
>             Fix For: current
>
>
> 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.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6902) Errors fetching from remote repos don't fail the build

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140579#action_140579 ]

jlongman commented on HUDSON-6902:
----------------------------------

[again|http://issues.hudson-ci.org/browse/HUDSON-5216?focusedCommentId=134758&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_134758]

Why would a build succeed if ANY of the source repositories fail?  Is there any scenario where this makes sense?  Have people said they would be happy if the build continued silently with out-of-date code?  

(Who are these people?  I want to make sure I never submit a job application to them... :-))

> Errors fetching from remote repos don't fail the build
> ------------------------------------------------------
>
>                 Key: HUDSON-6902
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6902
>             Project: Hudson
>          Issue Type: Bug
>          Components: git
>    Affects Versions: current
>         Environment: Ubunbu Karmic
>            Reporter: ieure
>            Assignee: abayer
>             Fix For: current
>
>
> 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.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-6902) Errors fetching from remote repos don't fail the build

Hudson issues mailing list
In reply to this post by Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-6902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140581#action_140581 ]

abayer commented on HUDSON-6902:
--------------------------------

I can see situations where you're pulling from multiple repos, and if one of those repos should happen to be inaccessible or go away, that shouldn't stop the build from proceeding. But I definitely agree that there's a problem if *no* repo can succeed. And given that most configurations are going to just have the one repo anyway...

> Errors fetching from remote repos don't fail the build
> ------------------------------------------------------
>
>                 Key: HUDSON-6902
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-6902
>             Project: Hudson
>          Issue Type: Bug
>          Components: git
>    Affects Versions: current
>         Environment: Ubunbu Karmic
>            Reporter: ieure
>            Assignee: abayer
>             Fix For: current
>
>
> 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.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]