Let's now edit the generated ClickStart application to customize it according to our needs. The first thing to do is to get the source code to amend it with our own stuff.
We assume you have a Git client installed on your computer or use an appropriate IDE integration.
Note
ClickStart always uses Git for repositories. The CloudBees forge also supports subversion, and maybe you prefer another SCM, such as Mercurial. There is no enforcement to use Git, and you can switch to your favorite SCM just by changing the Jenkins job SCM configuration. CloudBees just doesn't provide this option in ClickStart. If you don't want to use Git, you'll need to export the skeleton project and commit code into your own repository.
The ClickStart wizard gives us the forge repository URL. Pick it up and use it to clone your project. To use SSH, you need to have a key generated and registered on the CloudBees user settings page as discussed earlier. If you don't have one, you can use HTTPS with your...