[Bamboo Knowledge Base]
When Bamboo is integrated with Atlassian's Stash, you can:
A user who has edit privileges for a plan can make links to source-code files available by connecting the plan to the source repository, as described below.
There are two ways to link Bamboo to a Stash repository:
Configure an application link: If you have not previously configured an application link between your Bamboo and Stash servers, you will need to do so before you can add a linked repository.
See Linking to another application for more information.We recommend that you use OAuth for authentication for your link. If you have an existing link that uses a different authentication type, you can also configure OAuth authentication for the link.
To link a new Stash repository using the Administration menu:
Complete the required information:
Display name | A name that identifies this repository within Bamboo |
---|---|
Stash server | This menu will show all Stash servers that have been linked to Bamboo via an application link |
Repository | The repository that will be built. This menu will show all repositories on the Stash server that you have permissions to access. |
Branch | Pick a branch if you want to check out code from a branch other than the default branch. |
Advanced options
Use shallow clones | Allows Bamboo to perform shallow clones (i.e. history truncated to a specified number of revisions). This should increase the speed of the initial code checkouts, however if your build depends on the full repository history, we recommend that you do not use this option. Shallow clones are enabled by default. |
---|---|
Enable repository caching on remote agents | Allow caching of repositories on remote agents to save bandwidth. Note that caches are always full clones of the source repository. |
Use submodules | Select to enable submodules support if these are defined for the repository. If native Git capability is not defined for agent submodules support will be disabled. |
Command timeout | This is useful to stop hung Bitbucket processes. On slower networks, you may consider increasing the default timeout to allow Bamboo time to make an initial clone of the Git repository. |
Verbose logs | Turns on more verbose logs from Git commands. Use this option if you encounter problems with Git in Bamboo. |
Fetch whole repository | Fetches whole repository instead of only one selected branch. |
Enable Quiet Period | Specifies a delay after a single commit is detected before the build is started. This allows multiple commits to be aggregated into a single build. |
Include/Exclude Files | Allows you to specify the files that Bamboo should, or should not, use to detect changes. When you configure the Include option, it means that you want Bamboo to use only the mentioned files for change detection because by default Bamboo checks all the files. The same way, if you configure the Exclude option, Bamboo will not consider the excluded files for detecting changes. Enter into File Pattern a regular expression to match the files that Bamboo includes or excludes. The regex pattern must match the file path in the repository. See sub page for examples. |
Exclude changesets | Enter a regular expression to match the commit messages for changesets that should not start a build. |
Web Repository | If your repository can be viewed in a web browser, select the repository type. This allows links to relevant files to be displayed in the 'Code Changes' section of a build result. |
Stash – specify the following details for the repository:
See Integrating Bamboo with Stash for more information. |