Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41381

Allow for passing of secrets to startup scripts

XMLWordPrintable

      It would be great to be able to pass secrets to the VM startups scripts.

          [JENKINS-41381] Allow for passing of secrets to startup scripts

          Matthew Mitchell created issue -
          Dayang Shen made changes -
          Assignee Original: Claudiu Guiman [ clguiman ] New: Dayang Shen [ dayshen ]
          Pui Chee Chan made changes -
          Labels New: azure-jenkins in-progress
          Dayang Shen made changes -
          Assignee Original: Dayang Shen [ dayshen ] New: Azure DevOps [ azure_devops ]
          Azure DevOps made changes -
          Assignee Original: Azure DevOps [ azure_devops ] New: Chenyang Liu [ zackliu ]
          Azure DevOps made changes -
          Labels Original: azure-jenkins in-progress New: added-to-backlog azure-jenkins
          Azure DevOps made changes -
          Comment [ Low priority now, we'll consider it in future. ]
          Azure DevOps made changes -
          Labels Original: added-to-backlog azure-jenkins New: azure-jenkins

          Azure DevOps added a comment -

          mmitche could give more details about this request?

          Azure DevOps added a comment - mmitche could give more details about this request?

          Nick Jones added a comment -

          I'm not sure if this is what mmitche intended, but in my case I'd find it very valuable to be able to bind existing Jenkins credentials (aka "secrets" – username/password, secret text, etc.) and use them within the initialization scripts. For example, when I provision my Windows agents, I need to establish a NuGet source that requires a username and password, and currently that password must be hard-coded into every initialization script field (for each template that needs it).

          Nick Jones added a comment - I'm not sure if this is what mmitche intended, but in my case I'd find it very valuable to be able to bind existing Jenkins credentials (aka "secrets" – username/password, secret text, etc.) and use them within the initialization scripts. For example, when I provision my Windows agents, I need to establish a NuGet source that requires a username and password, and currently that password must be hard-coded into every initialization script field (for each template that needs it).

            zackliu Chenyang Liu
            mmitche Matthew Mitchell
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: