Failing a single entry should not stop the others

[Itxaka]

Hey there, awesome project.

We are currently evaluating it for Hadron (http://github/com/kairos-io/hadron) and it looks like a perfect fit for our use case, but testing it locally Im seeing that some failures in some entries prevent the whole thing from continuing?

$ bump update -v
Bumpfile:139: autoconf: error response: 502 Bad Gateway
Bumpfile:141: parted: error response: 502 Bad Gateway
Bumpfile:58: bison: error response: 502 Bad Gateway
Bumpfile:110: sudo: error response: 522 

I would expect that a single failure in there would not affect the others, to account for network issues and such, but it seems that it never updated anything. We have a kind of big list of various pieces of software, and some of those depend on external pages that may or may not be working at some points, so I woudl expect it to try to update the versions that it found updated while letting the user know about the errors it encountered.

Is this expected? Or this is something wanted? I could send a PR to improve this and continue updating/diff/checking even if they are failures, maybe with a flag --continue-on-error as to not change the current behaviour?

Cheers!

[wader]

Hey, thanks! nope continue on pipeline errors by default seems reasonable to me also. Had a quick look and i think most changes is probably how *Fileset.UpdateActions/Latest works. Have you started look into it? feel free to send a WIP PR if you wan to discuss things.

BTW when used as a github action it will also abort on first error, that i've thought about fixing for a while. But that can probably be improved separately.

[Itxaka]

Hey, thanks! nope continue on pipeline errors by default seems reasonable to me also. Had a quick look and i think most changes is probably how *Fileset.UpdateActions/Latest works. Have you started look into it? feel free to send a WIP PR if you wan to discuss things.

BTW when used as a github action it will also abort on first error, that i've thought about fixing for a while. But that can probably be improved separately.

Not yet, I had no time as I was writing the whole bumpfile and still are but I cant take a swing at it :D

[wader]

I see! great, no worries, did you mean "can" or "cant"? :)

[Itxaka]

I see! great, no worries, did you mean "can" or "cant"? :)

wooop, I mean can :D