When using the plugin on kubernetes based agents, all logs are duplicated.
This is introduced by https://github.com/jfrog/jenkins-jfrog-plugin/pull/63/files, where custom stdout handling was introduced to be able to extract the build info URL.
However, this does not work well with kubernetes agents. When the launcher provided by the kubernetes agent detects a custom stdout in the procstarter, it automatically does its own teeing, causing duplicate logs. Not sure if this is a bug in the kubernetes agent
This PR does not fix the problem, but reduces it's impact. Stdout tweaking is only done for the build publish command. Other commands (like eg mvn build) are untouched.
When using the plugin on kubernetes based agents, all logs are duplicated. This is introduced by https://github.com/jfrog/jenkins-jfrog-plugin/pull/63/files, where custom stdout handling was introduced to be able to extract the build info URL.
However, this does not work well with kubernetes agents. When the launcher provided by the kubernetes agent detects a custom stdout in the procstarter, it automatically does its own teeing, causing duplicate logs. Not sure if this is a bug in the kubernetes agent
This PR does not fix the problem, but reduces it's impact. Stdout tweaking is only done for the build publish command. Other commands (like eg mvn build) are untouched.
More details in https://github.com/jfrog/jenkins-jfrog-plugin/issues/74