More use of substitution variables

[jbride]

Hi.
URLs to the author's systtest and prod environments are included in various Jenkins job config.xml files..
URLs to the author's ticket-monster git repo are also referenced in various Jenkins job config.xml files.
These config.xml files are modifiable via the Jenkins user interface.

This enhancement request is to allow the user of this demo to optionally provide substitution variables for these URLs. Instructions would still be additionally provided as how to how to modify these URLs via the Jenkins UI.
These variables could be used at build time and most likely (i think) also passed to the jenkins-ci docker container at startup.

[tqvarnst]

Thats a really good idea Jeff. However In order to make this work the user will also have to supply ssh keys that are authorized to do changed in the git repo (the ticket monster release step). But we can document that or fix it to use jenkins web UI for key management.

[jbride]

I agree Thomas.
Regarding ssh keys, i ended up needing to leverage ssh keys for the two scenarios discussed in section 3.3.1 of my latest docs .
Also related to ssh keys, I originally thought that i could use the jenkins web UI for key management to push commits to my ticket-monster repo in my github account. Turns out I could not get this to work because its actually the mvn release plugin that is initiating the git push commands (not jenkins). Subsequently, i ended up adding a ~/.ssh/config for the jenkins OS user in the demo_jenkins_1 container to allow maven to push to github automatically.

Curious if you had similar issues ?