-
Improvement
-
Resolution: Fixed
-
Major
-
None
The current kubernetes-client library doesn't properly support the `error` websocket channel, merging it into stderr instead.
Because of this, getting the proper return code of a `sh` step involved parsing stderr, string manipulation, breaking other plugins that rely on stdout parsing too (e.g. pipeline-maven), and workarounds (https://github.com/jenkinsci/kubernetes-plugin/pull/242).
https://github.com/fabric8io/kubernetes-client/pull/1045 adds proper support to the error channel, so the returned information can be fetched separately. See https://github.com/kubernetes-client/python/issues/297 as an example.
- is blocking
-
JENKINS-49773 Pipeline plugin sh script returned exit code -2 from time to time
- Closed
-
JENKINS-39664 Docker builds do not work with Kubernetes Pipeline plugin
- Closed
-
JENKINS-49762 withMaven fails to detect maven executable in kubernetes container
- Closed
- relates to
-
JENKINS-54095 Extra character in output when running inside a container
- Closed
- links to