• Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • kubernetes-plugin
    • 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...

          [JENKINS-64268] Add ability to run pod without "steps"

          Vincent Latombe added a comment - - edited

          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.

          Vincent Latombe added a comment - - edited 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.

          Ah OK.  Unfortunate, but it is what it is.  Thank you!

          Camden Mamigonian added a comment - Ah OK.  Unfortunate, but it is what it is.  Thank you!

            Unassigned Unassigned
            cmamigonian Camden Mamigonian
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: