Daniel Santos_157bm4 Atlassian Team

Hi @Javier Lagarda I would be glad to test this if you could share part of your bitbucket-pipelines.yml file. Do you mind sharing part of the file with us?

Hi @Niket Chandrawanshi I guess the document that will provide you with the most meaningful information to understand pipelines structure is this one: * Configure bitbucket-pipelines.yml - Atlassian Documentation Let me share some examples that can be used as a reference so you know what are the changes you need perform in…

Hi @matgry This is the one: * [BAM-20536] Update YAML reference misleading information about notifications Let me know if you need anything else in this matter.

Hi @matgry Thank you so much for the feedback. I'll open another ticket to request this update in our docs.

Hi @Vinh Hong You need to add bamboo-specs/bamboo.yaml in the root of the source repository used to checkout your code in Bamboo. YAML specs is only able to process one repository and this repository needs to be the same where the bamboo.yaml file is located. YAML Localization Every YAML Specs file should be inside…

Hi @matgry The absence of examples happens because there is no implementation for plan notifications at the moment. I was able to talk to one of our developers and this feature was postponed due to possible design conflicts with other feature that is still in course of conclusion. That is the reason we have notifications…

Hi @[deleted] I'm glad you were already finding your own way! I wanted to share those examples as a reference for other users as well. Thank you for taking the time to create this question and following up on it, I appreciate that. Have a good one!

Hi @[deleted] I think the problem you are facing is caused by indentation. The common step behaves like a full step, not only an extra command in the script section. I understand you when you say that there is no validation error in the syntax but there are compilation errors. This is caused by a problem to validate files…

Hi @Carol Serroul Thank you for coming back to share the good news! I'm happy to be able to help =] Have a great day!

Hi @Arjun Gandhi I assume you are talking about Bitbucket cloud (bitbucket.org). You can still use Bamboo 5.14 with Bitbucket cloud but in this case, you will need to configure your repositories as Git repositories, instead of Bitbucket Cloud ones. This will allow you to check out your code as expected. Repositories…

Hi @[deleted] I think I got your point, but that is not how Bamboo permissions are designed. No user can create a repository without the Create Repository permission. That is the same rule we have for users accessing Bamboo through the UI. Administering the plan will allow you to link an existing linked repository to a…

Hi @Joe liu I'm assuming you are talking about a pull request that was merged in Bitbucket with pipelines configured. Is that correct? If it is, then you should have a branch trigger configured in your bitbucket-pipelines script. Can you share your pipelines script with us?

Hi @aksata The best approach is to create another release. I say that because Bamboo was designed in a way that releases are snapshots of something that happened in the past and will not be changed. We create a release when a build is ready to be deployed. I was running some tests here and if there is no release after the…

Maybe running them as a manual stage? That would allow you to update a green build (green, but which still have stages to run) to a failed one in case that stage fails. Maybe your integration tests will take a lot to run and you don't want them to run every time... I'm just trying to provide you with a suggestion that may…

I'm glad it was helpful! =]

For sure!!! =]

Hi @Mike Martinez I would be glad to help you if I could see what is the error message you get. Are there any error messages? Can you share them with us?

Hi @stellarweb-studio I'm not sure if I can help you with this one, but I'm curious about something. How is Cypress resolving the address http://web?

Hi @Kevin Matlock The issue you are facing seems to be caused by a missing permission configuration in your linked specs repository. Do you mind checking if the specs linked repo has the Repository configuration >> Permissions >> Bamboo Specs repositories access configured as expected for the repositories that your plan is…

Hi @Vineesh It is possible that the script you are running is not finishing. Have you run this script on windows terminal from outside Bamboo to check how it behaves? Are you able to stop the build by going to Actions >> Stop Build ?

We can't change the status of a build unless we run it again and it fails. Without knowing your environment I would risk saying that your integration test should be part of the build plan you want to change the status. This would make this plan fail when the integration test fails. Does that make sense?

Hi @Anton Egorov You won't be able to use Bamboo triggers to achieve this, as you already know. What you can do instead is to configure your server cron or even create a special plan in Bamboo that will serve as your cron to call the following REST API: curl --user <USER>:<PASSWORD> --data "bamboo.variable=value" -X POST…

Hi @schow-lmi3d To create the label you could use a call like: curl -X POST --user <USER>:<PASSWD> -H "Content-Type: application/json" -d '{"name":"new-label"}' <BAMBOO_URL>/rest/api/latest/result/<BUILD-KEY>/label Regarding the change of build status. Are you trying to start, stop, rerun builds? What would be the change…

Hi @Greg Noble I guess that is not a Pipeline specific question, but an SSH/SCP question. I assume you are trying to start the connection from pipelines, right? In order for that to work, you will need that your machine is reachable from the internet so the pipeline container can connect with it. Another option is that…

Hey @Rich Allen, What do you think of sharing your knowledge on setting up Drupal with this user? https://community.atlassian.com/t5/Bitbucket-questions/Drupal-7-deployment/qaq-p/1133074 Drupal is not my area of expertise and that is why I'm encouraging you to share your knowledge there if you have time for that of course.…

I'm passioned about this topic because I struggle with it. I totally agree with you @Teodora V _Warsaw Dynamics_ and you did such a great job connecting different perspectives on your comment. I guess we all know the reasons we do what we do but some times we just forget part of them to avoid the inner conflict. People are…

Hi @Sentinel, That is a great solution and thank you for taking the time to share it here. You found your own way to solve the problem and that is awesome! Have a good one!

In my test I just configured the Repository settings >> Webhooks >> Payload URL field with the URL above, of course, with the right plan and server address. You need to be admin of the GitHub repository for that.

Hi @Vineesh, I'm not sure if I understood your problem. Can you explain better this part? (...) it is working only when the plan is stopped( ie, Only when all plans are stopped and commit the code in git, it is automatically check-out the source code running the python file.) I guess you are following the configuration for…

Yeah, I learned that from this question. Thank you for the opportunity you gave me. Have a good one!