Git
Repository URL
...
Using
The Using drop down is populated with any property collector whose namespace matches the pattern defined by the Git plugin. The pattern for this action is ^git\..*
If you create a property collector for this action, make sure you select the Path Finder PlugIn type and give it a name that will match the pattern above in blue. Example names listed here, search the table's Plugin column for "Git".
For more in-depth explanations on property collectors see Property Collectors.
Alternatively, you can select the Custom option from the Using drop down list and specify a path in the resulting input field that will be displayed. Please read Why it's a good idea to use a property collector before using this option.
Branches
Branches To Monitor
...
Enter a non-zero value to hide old branches. Any branches which have no commits or builds within the specified number days will be excluded from the branch list on the Start Build and Trigger dialogs.
Tags
Tag Changes
Choose how to deal with tagged commits. You can choose to Ignore tags completely, Detect tags and show then next to changesets, or Detect and list as new changeset . The later option will create a new changeset in the database representing that a tag change (new tag, tag deletion or modification) was made. This new changeset can be used to trigger a build.
...
Run as Git hook
Tick to copy the script file to the Git hooks folder to be triggered by the Git post-checkout event. Leave this cleared to run the script directly after untracked files are cleaned up.
A script running as a Git post-checkout hook has access to the arguments passed in by Git, including refs of previous and new HEAD and flag indicating checkout type. Note however that the working folder may contain untracked files, which are cleaned up after checkout. You can specify paths to exclude from the clean up in the Post Checkout Output Paths field. This field accepts Ant patterns to specify multiple file paths.
Run shell login files
Tick to use the --login shell command option to execute login shell startup files when running the script directly.
Restricted shell
Tick to use the --restricted shell command option to start a restricted shell environment when running the script directly.
Use POSIX standard
Tick to use the --posix shell command option to change the behaviour to match the POSIX standard when running the script directly.
Script Arguments
Enter any arguments to wish to pass to the post-checkout script here.
Options
Use author name
Use the author name instead of committer name as changeset user.
Allow insecure certificates
Allow insecure (such as self-signed) SSL certificates.
Write changeset details to file
Tick to write changeset details to the file "_CI_ChangesetDetails.xml" after checking out each changeset.