| The git plugin and git client plugin support username / password credentials (with https protocol URL's) and private key credentials (with ssh and scp protocol URL's). Can you explain in more detail how you envision "secret key credentials" would work? The "Injecting Secrets into Jenkins Builds" describes three techniques to inject credentials into a job. The first, username / password, is supported by the git plugin and git client plugin. The second, "secret file", seems like it would need significantly more definition of how to express the interaction between the contents of the "secret file" and the git program. Are the contents of the secret file intended to be a private key? If so, they why not express that directly as a private key credentials? Are the contents of the secret file intended to be a username / password pair? If so, then why not express that directly using a username / password credential? The third "secret text", seems like it would require defining a convention for the environment variable(s) which would carry the private key or the username / password to the git command. Please clarify how the user of a "secret file" or a "secret text" would use them with the git plugin |
