-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
Right now Jenkins forces us to use container images with a shell in order to run the "steps" block. But some images I want to run, such as container-structure-test, don't have a shell (yeah, there's a debug version with a shell but there's another problem in there), and I'd like to have my stage "steps" be the "command" specified in my pod yaml.
Maybe this is a more fundamental Jenkins improvement rather than just the Kubernetes plugin...
Can't be covered by this plugin. Any pipeline step involves having a Jenkins agent and a remoting channel. Running steps as commands in containers is a completely different paradigm. It would only work with shell steps anyway.
Maybe consider https://github.com/jenkinsci/tekton-client-plugin but it's a PoC.