Feature/advanced error handling

[artemlive]

Here is the issue with the detailed description of this improvement: #293

[stakater-user]

@artemlive Yikes! You better fix it before anyone else finds out! Build 1 has Failed!

[stakater-user]

@artemlive Yikes! You better fix it before anyone else finds out! Build 2 has Failed!

[stakater-user]

@artemlive Yikes! You better fix it before anyone else finds out! Build 3 has Failed!

[stakater-user]

@artemlive Yikes! You better fix it before anyone else finds out! Build 4 has Failed!

[stakater-user]

@artemlive Yikes! You better fix it before anyone else finds out! Build 5 has Failed!

[stakater-user]

@artemlive Yikes! You better fix it before anyone else finds out! Build 6 has Failed!

[stakater-user]

@artemlive Yikes! You better fix it before anyone else finds out! Build 7 has Failed!

[artemlive]

Strange thing, because all tests have been passed locally.

time make test &> /dev/null; echo $?

real 0m42.501s user 0m35.419s sys 0m8.937s 0

[stakater-user]

@artemlive Yikes! You better fix it before anyone else finds out! Build 8 has Failed!

[stakater-user]

@artemlive Yikes! You better fix it before anyone else finds out! Build 9 has Failed!

[artemlive]

Linter, tests, and builds are fine I see the mistake in Makefile in the verify section. At least in my local env, it doesn't work because the project doesn't have "test" directory. All other stuff is the same and it works locally. Could someone tell me what exact problem with the last build and why Jenkins build has been failed. Thank you!

[stakater-user]

@artemlive Yikes! You better fix it before anyone else finds out! Build 10 has Failed!

[ahmedwaleedmalik]

Hi @artemlive, everything was fine but the test cases were failing against a different provider. I am looking into it and hopefully will resolve that today. In future, we will move to github actions so that anyone can view the pipeline and there is no inconvenience of such sorts. I'll try to get this prioritized !

[stakater-user]

@artemlive Image is available for testing. docker pull stakater/ingressmonitorcontroller:SNAPSHOT-PR-294-12

[rasheedamir]

@artemlive can you plz resolve the conflicts and lets get this merged?

[rasheedamir]

@artemlive any plans to update this PR?

[artemlive]

@rasheedamir Hello, yes, I'll try to fix all of them this week.

[tomjohnburton]

Any update on this?? Would be great to have

[mmiller1]

I'm glad I found this PR, I was about to start working on something similar. Any chance this will make progress soon?

[bilby91]

Is there any ETA for merging this PR and releasing a new version?

Thanks!

[julien-michaud]

Hello, we also would like this PR to be merged, thanks for your help !

[artemlive]

Hello, folks! I'm sorry for being gone so long. I'll review all the code and fix the conflicts as soon as possible.

[karl-johan-grahn]

@artemlive have you had time to look at this again?

[davidgibbons]

@artemlive Any chance you'll get time to actually look at this soon?

[andreas-mueller-bb]

@artemlive I would also be very curious if there is any update to this matter? :)