For example, the tag to push might be $BUILD_TAG, my-tag-$BUILD_NUMBER, build-$BUILD_NUMBER-from-$NODE_NAME, or a-very-specific-string-that-will-be-used-once. The name may include Jenkins environment variables or may be a fixed string.

Name of the tag to be pushed from the local workspace to the remote repository. Git will only download recent history of the project, saving time and disk space. Git will not download the complete history of the project, saving time and disk space. Default is to use a single thread for submodule updates Number of parallel processes to be used when updating submodules.

Number of threads to use when updating submodules This option overrides the default timeout. Specify a timeout (in minutes) for submodules operations. Timeout (in minutes) for submodule operations See the combining repositories section for more details. A reference repository may contain multiple subprojects. This option will be ignored if the folder is not available on the agent running the build. Path of the reference repo to use during submodule updateįolder containing a repository that will be used by git as a reference during submodule clone operations. If the parent project is cloned with ssh, then the authenticated submodule references must use ssh as well. If the parent project is cloned with https, then the authenticated submodule references must use https as well. Submodule credentials require that the submodule repository must accept the same credentials as the parent project. Enabling this extension will provide the parent repository credentials to each of the submodule repositories. Submodule updates do not use credentials by default. Use credentials from the default remote of the parent project. Use credentials from default remote of parent repository Retrieve the tip of the configured branch in. Update tracking submodules to tip of branch Without this option, submodules which contain other submodules will ignore the contained submodules. Specify a timeout (in minutes) for clone and fetch operations.ĭeselect this to perform a clone without tags, saving time and disk space when you want to access only what is specified by the refspec, without considering any repository tags. Timeout (in minutes) for clone and fetch operations This option will be ignored if the folder is not available on the agent. Specify a folder containing a repository that will be used by git as a reference during clone operations. Path of the reference repo to use during clone Git will only download depth commits from the remote repository, saving time and disk space. Set shallow clone depth to the specified number of commits. This can save time and disk space when you just want to access the latest version of a repository.

Git will not download the complete history of the project. Perform a shallow clone by requesting a limited number of commits from the tip of the requested branch(es). If this is not enabled, then the plugin default refspec includes all remote branches. This can save time, data transfer and disk space when you only need to access the references specified by the refspec. Perform initial clone using the refspec defined for the repository.

Git submodule untracked content