Following build logs creates 1 socket/second & duplicate log data about jenkins-plugin HOT 3 CLOSED

Hmmm ... i thought @jim-minter fixed duplicate log data with 7da5503 - do you have this commit in your env ?

from jenkins-plugin.

Ah, no I don't. That will work in the vast majority of runs, but it is still non-deterministic because it relies on a momentary build state.

from jenkins-plugin.

OK, given @jim-minter 's change covers the vast majority, I've marked a p3.

As an fyi, up until a couple of months ago, the restclient's pod logging depended on the oc binary being present, so we had our own polling mechanism that did simply http requests against the build log endpoint, and we could manage the edge cases more directly.

So let's see how the discussion you started goes. If it doesn't go the way we want it, we can always revert to our former bypass path if it ends up cleaner than the retry approach with the Pod logging @jupierce noted.

@jupierce and I have talked, and given the significant amount of leg work he's already done, he's agreed to take ownership of this one. Thanks!

from jenkins-plugin.