Custom container instead of Inbound-agent

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

XMLWordPrintable

      I would like to know what is the best practice to use a custom container (other than the default one inbound-agent) in a job or pipeline.

      Also, is it possible to base the custom container on SSH protocol instead of JNLP ?

            Assignee:
            Unassigned
            Reporter:
            Paul MARTEL
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: