JNLP container is launched with default arguments even with an explicit container definition

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Since Kubernetes plugin 1.5.2, this pipeline script:

       

      podTemplate (
          cloud: 'my-cloud',
          label: 'my-pod',
          containers: [
              containerTemplate(
                  name: 'jnlp',
                  image: 'my-image')]
      ) {
          // ...
      }
      

      will run my-image with the default command line arguments, namely the node secret and node name. Prior to this version, it would run the image with no arguments.

      This is a problem for me, because my image gets confused by the additional arguments. I think this should be considered a regression.

            Assignee:
            Carlos Sanchez
            Reporter:
            Roman Donchenko
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: