Thanks Mark, yeah this is one option but in this case, username and
password are visible in console output. I am thinking to use SSH Keys.
On Monday, 2 October 2017 13:46:24 UTC+11, Mark Waite wrote:
>
> If your GIT_URL is https, then you could embed the username and password
> into the URL.
If your GIT_URL is https, then you could embed the username and password
into the URL. For example, the URL:
https://github.com/user/repo
can be
https://username:passw...@github.com/user/repo
Mark Waite
On Sun, Oct 1, 2017 at 8:36 PM Vikas Kumar wrote:
> We are
We are trying to use AWS DynamoDB (with KMS encrypted values) to store our
secrets rather than using Jenkins Credentials. This is advised by our
security team.
I am able to fetch secrets (git username and password) as variables on
Jenkins slaves, but not sure how to use those to *checkout*
Hi all,
Just FYI, Jenkins Windows Service command line is documented here:
https://github.com/kohsuke/winsw .
WinSW is a standalone project, Jenkins just generates an XML configuration
file for it. You can take the template from here