QuickBuild utilizes the Git command (git) to interact with remote Git repository. If this command is not in system path, you will need to specify location of the command by configuring Git plugin as below:
Further more, Git command (git) location can be specified on a per-node basis by following below steps:
NOTE: example above is just for demonstration, you can use any other user attribute name instead of gitPath.
You may refer to this page on how to add a repository.
Currently, below URL prefixes are supported:
If https is used, and your credential need password, you need first add the credential manually to the nodes which you want check out code to.
Your developers might need to push their local commits in local repository to a central official Git repository occasionally. In this case, QuickBuild can validate these commits by running proof build before pushing them.
Since proof build set up is a bit tricky, we first set up proof build for the administrator account and make sure it works before we proceed to enable it for all developers. To set up proof build for administrator, please follow below steps:
Now proof build has been enabled for your account, please make some local commits into your local repository specified above, and then run the test configuration. If set up correctly, your local commits will be picked up and reflected in the build result. A local change tab will also appear to display local commits after build finishes. Your local commits will be pushed automatically if build is successful.
Now that we have a concept of how proof build works. In order to get proof build works for all developers, we need to parameterize various proof build properties, so that different properties can be used for different developers. To do this, you will need to:
In this way, various proof build properties will be prompted when your developer runs the build. Once they've been specified by your developer for the first time, the values will be remembered for subsequent triggers for that user.
At last we suggest to set up the configuration to enable concurrent builds so that multiple builds in the same configuration can run concurrently. This is vital to get fast feedback in case multiple developers are requesting proof builds in the same time.