youngmon/atlassian-qna huggingface dataset:
bamboo-spec include not working for common job
Asked by Dave Attard:

I have build plans working with bamboo-specs and i would like to pull out the common parts into an include. I have read and re-read the specs and i cant work it out

```
bamboo-specs
| - bamboo.yml
| - Services
    | - build-ServiceA.yml
??  | - build-ServiceB.yml
| - Common
    | - build-job.yml
```

```
---
!include 'Services\build-ServiceA.yml'
---
!include 'Services\build-ServiceB.yml'
```

folder\\build-ServiceA.yml-\> working

```
---
version: 2
plan:
  project-key: XXX
  key: XXXXX
  name: Build Service
stages:
- Build:
    jobs:
    - Build-Service
Build-Service:
  key: JOB1
  tasks:
  - clean
  - script:
      interpreter: WINDOWS_POWER_SHELL
      scripts:
      - |-
        Set-Location ./${bamboo.solution}
        dotnet restore -v q
      description: Restore
  - script:
      interpreter: WINDOWS_POWER_SHELL
      scripts:
      - |-
        Set-Location ./${bamboo.solution}/${bamboo.serviceFolder}
        dotnet publish -c Release -v q -o ${bamboo.working.directory}/packages
        description: publish
  artifacts:
  - name: ${bamboo.solution}
    location: packages
    pattern: '**/*'
    shared: true
    required: true
  artifact-subscriptions: []
variables:
  solution: service
  serviceFolder: folder
triggers: []
repositories:
- Repo
branches:
  create:
    for-new-branch: (release|feature)/.+
  delete:
    after-deleted-days: 1
    after-inactive-days: 30
  link-to-jira: true
```

What i would like to do is move the Build-Service job into a common include file. Looking at the spec information on [includes](https://docs.atlassian.com/bamboo-specs-docs/9.2.1/specs.html?yaml#includes) i should be able to do this. However when i make the changes. i have tried

* Build-Service: !include '..\\common\\build-job.yml'
* Build-Service: !include 'common\\build-job.yml'

folder\\build-ServiceA.yml-\> error

```
Bamboo YAML import failed: Invalid format of the YAML file: Include file ..\COMMON\build-job.yml does not exist
```

```
---
version: 2
plan:
  project-key: XXX
  key: XXXXX
  name: Build Service
stages:
- Build:
  jobs:
  - Build-Service

Build-Service: !include '..\common\build-job.yml'

triggers: []
repositories:
- Repo
branches:
  create:
    for-new-branch: (release|feature)/.+
  delete:
    after-deleted-days: 1
    after-inactive-days: 30
  link-to-jira: true
```

common\\build-job.yml

```
  tasks:
  - clean
  - script:
      interpreter: WINDOWS_POWER_SHELL
      scripts:
      - |-
        Set-Location ./${bamboo.solution}
        dotnet restore -v q
        description: Restore
  - script:
      interpreter: WINDOWS_POWER_SHELL
      scripts:
      - |-
        Set-Location ./${bamboo.solution}/${bamboo.serviceFolder}
        dotnet publish -c Release -v q -o ${bamboo.working.directory}/packages
      description: publish
  artifacts:
  - name: ${bamboo.solution}
    location: packages
    pattern: '**/*'
    shared: true
    required: true
  artifact-subscriptions: []
```


Answers:
author: Dave Attard
body: <https://community.atlassian.com/t5/Bamboo-questions/bamboo-spec-include-not-working-for-common-job/qaq-p/2279194>


Tags: server
convert bamboo plan to gitlab-ci
Asked by Farhad:

Dear All

Our company work with Bamboo for create CI/CD pipeline. but we can move from Bamboo to gitlab and i want convert all Bamboo Script in build stage and push stage (attached as images) to gitlab-ci file. could you please help me for this task ?

<https://stackoverflow.com/questions/75498706/convert-bamboo-plan-stages-to-gitlab-ci-file>

Thanks


Answers:
author: Eduardo Alvarenga
body: Hello [@Farhad](/t5/user/viewprofilepage/user-id/5154009),

Welcome to **Atlassian Community**!

Though I can't really walk you through how to create an equivalent Bamboo Plan in GitLab CI format as I personally don't know that format, I can give you some tips on how to export it in a programmatic way from Bamboo and then do the conversion.

Bamboo allows you to export a Plan in two formats, Java and YAML. Please check the following links for instructions on how to proceed.

* [Exporting existing plan configuration to Bamboo Java Specs](https://confluence.atlassian.com/bamboo/exporting-existing-plan-configurations-to-bamboo-specs-894743917.html)
* [Exporting existing plan configuration to Bamboo YAML Specs](https://confluence.atlassian.com/bamboo/exporting-existing-plan-configuration-to-bamboo-yaml-specs-1018270696.html)

Java Specs format will contain all the settings of a plan, while YAML Specs format may miss some specific parts as the functionality hasn't been fully implemented yet. Please consider both formats and choose the one that fits you better.

Sincerely,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**

comments: author: Farhad
body: Thanks [@Eduardo Alvarenga](/t5/user/viewprofilepage/user-id/4365410) for your respond.
bamboo-spec include not working for common job
Asked by Dave Attard:

I have build plans working with bamboo-specs and i would like to pull out the common parts into an include. I have read and re-read the specs and i cant work it out

```
bamboo-specs
| - bamboo.yml
| - Services
    | - build-ServiceA.yml
??  | - build-ServiceB.yml
| - Common
    | - build-job.yml
```

```
---
!include 'Services\build-ServiceA.yml'
---
!include 'Services\build-ServiceB.yml'
```

folder\\build-ServiceA.yml-\> working

```
---
version: 2
plan:
  project-key: XXX
  key: XXXXX
  name: Build Service
stages:
- Build:
    jobs:
    - Build-Service
Build-Service:
  key: JOB1
  tasks:
  - clean
  - script:
      interpreter: WINDOWS_POWER_SHELL
      scripts:
      - |-
        Set-Location ./${bamboo.solution}
        dotnet restore -v q
      description: Restore
  - script:
      interpreter: WINDOWS_POWER_SHELL
      scripts:
      - |-
        Set-Location ./${bamboo.solution}/${bamboo.serviceFolder}
        dotnet publish -c Release -v q -o ${bamboo.working.directory}/packages
        description: publish
  artifacts:
  - name: ${bamboo.solution}
    location: packages
    pattern: '**/*'
    shared: true
    required: true
  artifact-subscriptions: []
variables:
  solution: service
  serviceFolder: folder
triggers: []
repositories:
- Repo
branches:
  create:
    for-new-branch: (release|feature)/.+
  delete:
    after-deleted-days: 1
    after-inactive-days: 30
  link-to-jira: true
```

What i would like to do is move the Build-Service job into a common include file. Looking at the spec information on [includes](https://docs.atlassian.com/bamboo-specs-docs/9.2.1/specs.html?yaml#includes) i should be able to do this. However when i make the changes

folder\\build-ServiceA.yml-\> error

```
Bamboo YAML import failed: Invalid format of the YAML file: Include file ..\COMMON\build-job.yaml does not exist
```

```
---
version: 2
plan:
  project-key: XXX
  key: XXXXX
  name: Build Service
stages:
- Build:
  jobs:
  - Build-Service

Build-Service: !include '..\common\build-job.yml'

triggers: []
repositories:
- Repo
branches:
  create:
    for-new-branch: (release|feature)/.+
  delete:
    after-deleted-days: 1
    after-inactive-days: 30
  link-to-jira: true
```

common\\build-job.yml

```
  tasks:
  - clean
  - script:
      interpreter: WINDOWS_POWER_SHELL
      scripts:
      - |-
        Set-Location ./${bamboo.solution}
        dotnet restore -v q
        description: Restore
  - script:
      interpreter: WINDOWS_POWER_SHELL
      scripts:
      - |-
        Set-Location ./${bamboo.solution}/${bamboo.serviceFolder}
        dotnet publish -c Release -v q -o ${bamboo.working.directory}/packages
      description: publish
  artifacts:
  - name: ${bamboo.solution}
    location: packages
    pattern: '**/*'
    shared: true
    required: true
  artifact-subscriptions: []
```


Answers:
author: Dave Attard
body: ```
Build-Service: !include 'common\build-job.yml'
```


Tags: server

spec

yaml
MonoRepo with Linked repostitory
Asked by Dave Attard:

I have a MonoRepo and am trying to set up bamboo-specs, that will build only the service that is changed.

I have been able to do this with plan repository with change-detection; However, what i would like to do is have one Linked Repository, that all my plans use, and still have the file filter applied so only run the build plan for the folder that changes. I really dont want to set up 100's of "duplicate" linked repos with the change detection on them.

If it cant be done with the repo level, is there a change detection task that can be applied that will only run the rest of the tasks if condition is met

Repo

- Service1

- Service2

...

```
repositories:
- repo1:
    type: bitbucket-server
    server: Bitbucket
    project: XXXX
    slug: xxxx
    clone-url: 
    public-key: 
    private-key: 
    branch: master
    command-timeout-minutes: '30'
    use-shallow-clones: true
    cache-on-agents: true
    submodules: false
    ssh-key-applies-to-submodules: false
    verbose-logs: false
    fetch-all: false
    lfs: false
    change-detection:
      file-filter-type: include_only
      file-filter-pattern: Service1/.*
```


Answers:
author: Eduardo Alvarenga
body: Hello [@Dave Attard](/t5/user/viewprofilepage/user-id/5019157)

Having a monolithic architecture with dynamic triggers based on the content that has been modified is something that is not available in Bamboo.

As an alternative, you can set a single Plan that would be triggered on every commit of that mono repo and then Checkout the repository and initiate a Script Task that will analyse the last revision's contents and trigger the required builds in Bamboo over REST API.

For example, the following git command will return the list of the files modified in the HEAD revision:

```
$ git diff-tree --no-commit-id --name-only -r HEAD
```

Then, from that output you can make the script realise which Plans are to be triggered, then use the Bamboo REST API to initiate their builds:

* <https://developer.atlassian.com/server/bamboo/rest/api-group-api/#api-api-latest-queue-projectkey-buildkey-post>

That is a quite simple theory that would work for your case. You may have to extend the script to consider (and trigger) other branches in case you use Plan branches in Bamboo.

Sincerely,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**


Tags: monorepo

server

spec
No agent can build this job. Even when it is showing 1 agent available and has the matching capa...
Asked by Bhavya Shukla:

Agent is available and it is online. But when try to run any plan it is showing no agent can build this job.


Answers:
author: Eduardo Alvarenga
body: Hello [@Bhavya Shukla](/t5/user/viewprofilepage/user-id/4837436)

Inside the Plan configuration, check each Job's Requirements tab and see if there is any specific capability that is declared and missing on the Agent.

It can also be the case of an Agent that is dedicated to another Project/Plan/Job and will not build other unlinked Plans.

Sincerely,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**
Bamboo OnDemand Trigger Bitbucket Cloud repository not found
Asked by ???SA:

Hi there

According to this [url](https://confluence.atlassian.com/bamboo/trigger-a-bamboo-build-from-bitbucket-cloud-using-webhooks-873949130.html)

Configure your Bamboo plan to trigger a build using the Bitbucket Cloud repository trigger by selecting**Actions** \>**Configure plan** \>**Triggers** \>**Add trigger** \>**Bitbucket Cloud repository trigger** .

When I look at my server's trigger screen, there is not found **Bitbucket Cloud repository trigger** .

![?????????? 2023-02-21 ???? 8.15.29.png](https://community.atlassian.com/t5/image/serverpage/image-id/241351i4AE432AB18664867/image-size/large?v=v2&px=999 "?????????? 2023-02-21 ???? 8.15.29.png")

plz tell me how to solve it

thks.


Answers:
author: Eduardo Alvarenga
body: Hello [@???SA](/t5/user/viewprofilepage/user-id/5152256)

Welcome to **Atlassian Community**!

The Bitbucket Cloud integration is [a new feature](https://confluence.atlassian.com/display/BAMBOORELEASES/Bamboo+9.0+release+notes#Bamboo9.0releasenotes-bitbucket) introduced in Bamboo 9.0.

Based on the provided screenshot, it appears you are running Bamboo 8.2 or earlier.

For instructions on how to configure the trigger using Bitbucket Cloud and Bamboo earlier than 9.0, please check this page:

* [Bamboo 8.2 - Triggering a Bamboo build from Bitbucket Cloud using Webhooks](https://confluence.atlassian.com/bamboo0802/triggering-a-bamboo-build-from-bitbucket-cloud-using-webhooks-1103433030.html)

Best regards,

Eduardo Alvarenga  
Atlassian Support APAC

**--please don't forget to Accept the answer if the reply is helpful--**

comments: author: ???SA
body: Thanks!! I'll upgrade the version and try again :)
Can StatusPage send sample data to newly set up webhook URLs?
Asked by Ryan Marks:

I'm integrating a StatusPage site with Zapier. To configure the Zap correctly, the Zap webhook needs to receive data. If configuring the Zap for a business with a low rate of incidents, it may be some time to see any data in Zapier.

Would it be possible for StatusPage to send sample data to newly created webhook URLs?


Answers:
author: Shivam Naik
body: Hi [@Ryan Marks](/t5/user/viewprofilepage/user-id/5040205) ,

Happy to help!

It won't be possible to generate a test payload upon subscribing with that new Webhook subscription, however I would recommend creating a Statuspage trial and using that to test the Webhook out. You could create a new page, add the Webhook as a Subscription, and then create an Incident to test on Zapier. But again, unfortunately there isn't a button in the UI that would allow you to send a payload immediately, you would either have to wait for notifications to be sent out, or test it using an Incident on your page.

Please let me know if you have any follow up questions!

comments: author: Ryan Marks
body: Thank you for your reply.

Would it be possible to open a feature request for this functionality?


author: Shivam Naik
body: Hi [@Ryan Marks](/t5/user/viewprofilepage/user-id/5040205) ,

I have created one under STATUS-561 for the ability to send test notifications. This ticket is internal, but should it be added in a future release of the product, a notification will be sent out to product owners regarding it.

Please let me know if you have any follow up questions!


Tags: cloud

webhook

zapier
Good evening i ask some question how to resolved my account on cb,please help me..
Asked by wilma bacatcat:

**Good evining, i need help becouse my problem how to resolved my account on the cb account, i really love my job, i hopely you help how to do fix this my problem.**

**please give me clear answer my question. thank you so much.**

**meg35**


Answers:
author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

I am afraid your question does not make sense to us. We don't know what you mean by "CB account", and we don't know what you mean by "resolved my account".

Is CB an Atlassian-based system? If so, which one? Have you tried talking to your administrators about the problem?


Tags: cloud
Audience Specific Page Audience/Groups Vs Component Only
Asked by Charlie Escibar:

*** ** * ** ***

Using Statuspage Audience Specific Page. I currently use Audience/Groups to give access to components.   

I see you also have the ability to subscribe to component directly and I may want to take this approach instead of giving access based on Groups/Audience.

Question is what is the benefits of using Audience/Groups if you can subscribe to components directly?   

Since using groups/audience is limited based on your current package and components are not.


Answers:
author: Oday Rafeh
body: Hi [@Charlie Escibar](/t5/user/viewprofilepage/user-id/5095587) ,

Both Audience/Groups and direct Component subscriptions have their unique benefits in Statuspage, and the choice between them depends on your specific use case and organization's needs.

**Audience/Groups:**

**Better control and organization:** By using Audience/Groups, you can create specific groups of users with access to a particular set of components. This allows you to manage access more efficiently.

<br />

**Easier management:** When you want to update access for a group of users, you can do it in one place by editing the Audience/Group, rather than individually updating each user's component subscriptions.

<br />

**Granular access control:** Audience/Groups provide you with the ability to restrict access to certain components or pages, ensuring that only authorized users can view or receive notifications for those components.

<br />

**Direct Component Subscriptions:**

**Flexibility:** Subscribing to components directly allows users to choose which components they want to receive notifications for, based on their specific needs and preferences.

<br />

**Less administrative overhead:** Direct component subscriptions do not require you to manage groups or audiences, simplifying the overall management process.

<br />

**No limitations:** Unlike Audience/Groups, which may be limited based on your subscription package, there is no limit to the number of components that users can subscribe to directly.

Regards

Oday


Tags: cloud
Linked status page's
Asked by Andrew Michaelis:

I've referred you to several customers who now also have status pages.

But I can't have a status on my side be dependend on the status on their page.

Why is there not a 3rd party option to link to another status page? They are both owned and hosted by you?


Answers:
author: Oday Rafeh
body: Hi [@Andrew Michaelis](/t5/user/viewprofilepage/user-id/5173239) ,

Currently, **Atlassian Statuspage** doesn't have a **built-in feature** to link or create dependencies between different status pages directly.

there are some workarounds you can use to achieve a similar effect:

**Embedding status information:**

You can embed the status information from your customers' status pages onto your own page using custom **HTML/CSS/JavaScript**. (If you need help with that I can give you a hand )

This requires adding a custom component to your page and fetching the status data from your customers' status pages using their **Statuspage API.**

**Third-party integration or custom automation:**

You can explore the possibility of using **third-party integration** tools like **Zapier** or write **custom scripts** using the **Statuspage API** to automatically update your status page based on the changes in your customers' pages.

While these workarounds may not be as seamless as having a built-in feature, they can help you achieve a similar outcome.


Tags: cloud
Is it possible to have users only se the status of a component group?
Asked by James Parkin:

I'd like to be able to give some public users the ability to see only the status of a component group and not be able to expand the group to see the status of the actual components.

I'd like our customers to be able to see that we have a problem impacting an element of our service, but I don't need them to see which component it is that it impacting them.

I'm sure you used to be able to do this.


Answers:
author: Egor
body: Hey James,  
Thanks for reaching out to Atlassian Community!   

I'm afraid that it won't be possible to implement such a thing on a public page.   
Using our Audience-Specific page type, you can define what users can see based on their groups. Please see <https://www.atlassian.com/software/statuspage/audience-specific-pages>   

For the public page, with Component Groups, when a child component is in a non-Operational state, the default behavior is for the group to expand on the page and show all child component statuses. If someone wants to keep the component group collapsed, they can use one of the following in the **Custom header HTML** . This relies on a timer set to 0.

\<script\>  
$(function() {  
setTimeout(function () {  
$('.is-group.open \> .component-inner-container').click()  
}, 0);   
});  
\</script\>

It won't hide your components, but at least it won't automatically expand.   

You can also try to hide components by using page customizations. Here are a few examples that can help you - <https://support.atlassian.com/statuspage/docs/css-and-javascript-snippets-for-customizations/>   

I hope this helps.   

Best Regards,

Egor


Tags: cloud
Remove header "components affected"
Asked by Jacob B_:

Hi Team,

I was wondering if you could remove the header "components affected" in the mail sent out from Statuspage?

![status.png](/t5/image/serverpage/image-id/245892i75BFA0637A0DE072/image-size/large?v=v2&px=999 "status.png")


Answers:
author: Leonardo Barrios
body: Hello Jacob!!

Thank you for contacting the Atlassian community! I am Leo from Atlassian Team.

The ability to remove/edit this header for "Components affected" as well as "Start time", "Estimated duration" or "Time posted" that are also on the sent emails is not possible with the Statuspage product design.

The customization you are currently able to perform, you may refer to our article here:

[Customize email notifications \| Statuspage \| Atlassian Support](https://support.atlassian.com/statuspage/docs/customize-email-notifications/)

I hope this information helps you!

Best regards,  
Leonardo Barrios  
Support Engineer


Tags: cloud
Integrating a third party app to status page
Asked by Vaibhav V:

Hi Team,

I am trying to integrate a third party monitoring service(called as Site 24/7) to the status page apart from the one's already mentioned in the Atlassian marketplace(like Pingdom, Datadog , New Relic etc)., I have all the API key and required stuff of the third party tool to configure but I am exactly not sure how or from where we can start to achieve that.

Could any one of us please help me out or point me to any resource that would give the required information.?

Regards,

Vaibhav V


Answers:
author: Jesse Klein
body: Hello Vaibhav,

This is Jesse from the Statuspage support team. Thanks for the question regarding adding a third party service using the API. My understanding of your question is that you want to use the system metrics feature. If you are trying to add System Metrics similar to Pingdom, Datadog, and New Relic, you would need to add the data via the Metrics API: <https://developer.statuspage.io/#tag/metrics>

Essentially, you need to add metric data point for every 5 minutes at a minimum and you send us the timestamp and the value for each point. Your monitoring service would need to provide that data and that would depend on how it is set up. If you are able to send this information at regular intervals, you can get the metrics to show up. This article might also be helpful for you: <https://support.atlassian.com/statuspage/docs/what-are-system-metrics/#Example-metrics>

Please let me know if I am misunderstanding your question or if you have any additional questions. I hope you have a great day!

Regards,  
Jesse


Tags: cloud