-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
Problem
When we have multiple repositories it is often common that we need to know which repository triggered the build. This allows us to skip part of the work done in the build and saving time/money.
Suggested solution
Add a new variable that tells which branch triggered the build
Note
This information is already available as you can see in this Community post:
Without this variable, we can't use the Conditional tasks for Bamboo plugin to decide which task we want to avoid when a specific repo is triggered. This plugin only accepts Bamboo default variables, not injected ones. In other words, if we compare the variables as shared in the linked Community post we will not be able to use the information with an injected variable.
[BAM-20760] Add a new variable that tells us which repository triggered the build (used when a plan has multiple repos)
| Support reference count | New: 1 |
| Description |
Original:
h3. Problem
When we have multiple repositories it is often common that we need to know which repository triggered the build. This allows us to skip part of the work done in the build and saving time/money. h3. Suggested solution Add a new variable that tells which branch triggered the build h3. Note This information is already available as you can see in this Community post: * [Determine which Repo triggered a build|https://community.atlassian.com/t5/Bamboo-questions/Determine-which-Repo-triggered-a-build/qaq-p/1108462?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic] (i) Without this variable, we can't use the |
New:
h3. Problem
When we have multiple repositories it is often common that we need to know which repository triggered the build. This allows us to skip part of the work done in the build and saving time/money. h3. Suggested solution Add a new variable that tells which branch triggered the build h3. Note This information is already available as you can see in this Community post: * [Determine which Repo triggered a build|https://community.atlassian.com/t5/Bamboo-questions/Determine-which-Repo-triggered-a-build/qaq-p/1108462?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic] (!) Without this variable, we can't use the [Conditional tasks for Bamboo|https://marketplace.atlassian.com/apps/1219706/conditional-tasks-for-bamboo?hosting=server&tab=overview] plugin to decide which task we want to avoid when a specific repo is triggered. This plugin only accepts Bamboo default variables, not injected ones. In other words, if we compare the variables as shared in the linked Community post we will not be able to use the information with an injected variable. |
| Description |
Original:
h3. Problem
When we have multiple repositories it is often common that we need to know which repository triggered the build. This allows us to skip part of the work done in the build and saving time/money. h3. Suggested solution Add a new variable that tells which branch triggered the build h3. Note This information is already available as you can see in this Community post: * [Determine which Repo triggered a build|https://community.atlassian.com/t5/Bamboo-questions/Determine-which-Repo-triggered-a-build/qaq-p/1108462?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic] |
New:
h3. Problem
When we have multiple repositories it is often common that we need to know which repository triggered the build. This allows us to skip part of the work done in the build and saving time/money. h3. Suggested solution Add a new variable that tells which branch triggered the build h3. Note This information is already available as you can see in this Community post: * [Determine which Repo triggered a build|https://community.atlassian.com/t5/Bamboo-questions/Determine-which-Repo-triggered-a-build/qaq-p/1108462?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic] (i) Without this variable, we can't use the |