AFAIK, sauce-ondemand doesn't support Sauce Connect's tunnel identifiers. Tunnel identifiers ("-i") allow to use multiple concurrent tunnels for the same account.

      Currently, I can set fixed tunnel identifier by asetting "Sauce Connect Options" in "Sauce Connect Advanced Options", but I don't see any way to make it to depend on a variable. For me, it would be enough, if one could use environment variables in "Sauce Connect Options". For example, if I could set "Sauce Connect Options" to "-i ${EXECUTOR_NUMBER}" and that variable would be evaluated, I could have concurrent Jenkins jobs using the same Sauce Labs credentials and each Jenkins executor would use its own tunnel.

          [JENKINS-18860] Add support for Sauce Connect tunnel identifier

          Ross Rowe added a comment -

          Hi, thanks for raising this, I'll try to include this functionality in the next version of the plugin.

          Cheers,

          Ross

          Ross Rowe added a comment - Hi, thanks for raising this, I'll try to include this functionality in the next version of the plugin. Cheers, Ross

          Ross Rowe added a comment -

          Tunnel identifier can be set through the 'Sauce Connect Options' field on the Jenkins job configuration

          Ross Rowe added a comment - Tunnel identifier can be set through the 'Sauce Connect Options' field on the Jenkins job configuration

          Ross Rowe added a comment -

          Sorry, closed this issue in error

          Ross Rowe added a comment - Sorry, closed this issue in error

          Ross Rowe added a comment -

          This issue should be fixed in the latest version of the plugin

          Ross Rowe added a comment - This issue should be fixed in the latest version of the plugin

            rossrowe Ross Rowe
            datakurre Asko Soukka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: