Daniel Santos_157bm4 Atlassian Team

Hey @rahakaha This is what will work for the Bitbucket cloud search: Search >> Search for code project:<PROJECT_KEY> -repo:<REPO_SLUG_TO_AVOID> <TOKEN> e.g. project:RP -repo:maven-surefire-tests custom More details about the Bitbucket cloud search can be found here: Search for code in Bitbucket Server - Atlassian…

Hi @Teepers McGee After running some tests here we see that this message should only happen when the repository does not exist. * Can you please confirm if you are still able to clone this repo in the machine you were able to clone (at some point)? Please doublecheck there is no typo in the repository URL as well.

Hi @Fux Peter Every user with edit permissions in the pipelines repository will be able to edit the bitbucket-pipelines.yml file. This is due to the pipeline's design where the build configuration is embedded in the repository itself. This has lots of advantages in flexibility but has some trade-offs like this one.…

Hi @Simon I suppose your Repo A (main repository) will be triggered every time you update the links to commits present in your git submodules. In theory, every time you want those commits to be considered in the main repo you should update the links. Usually, we use submodules when we have an independent part of the…

Hi @Eduardo Huacuz Yes, you can do that if you put the token "[skip ci]" in all commit messages from your tool. A commit that would be skipped by pipelines could be created like: git commit -m "My message from automated tool [skip ci]" Reference: Bitbucket Pipelines FAQ - Atlassian Documentation ⚠️We have a bug that…

Maybe you don't need to identify the stage and can come with a different approach to solve your issue. I don't know why you need the stage name. If you share the problem you are trying to solve we may find a different solution. If you think there is no other solution, then the only option is to wait for BAM-20620. =]

That is great! I'm glad you already found a way to move on. Please vote on that ticket to increase the visibility of it among our developers. Have a good one! =]

I don't think you are doing anything wrong. The implementation is a startwith search as you already discovered. The second format call with the full key is not covered by the search. It makes sense since the PLAN-KEY is already present in the REST API call, but it could work if designed for that. This is how I was able to…

Hi @Anthony -Shadow- Elmore The issue you are facing happens due to the fact that account variables are not evaluated when a repository variable is declared mentioning the first one. I've opened an improvement request to cover this scenario: * [BCLOUD-19448] Evaluate account variables referenced by repository variables The…

Hi @Ieng Lao You should use just "deployment equals|match true". e.g.

Hi @François Guillot It was my bad, like an e-mail without attachments... This is the feature request I've opened: * [BAM-20620] Add variable with stage information during build time. Yes, I used the searchTerm to add the job key. When I tested I used only the last part of the job key. Something like:…

Hi @François Guillot In my tests, it worked with the full name and the job key. I know the search mechanism is startWith which some times will bring multiple results, but that is less likely to happen due to the fact that we are searching inside the same plan (restricted set of results). I've created this feature with the…

Hi @Christophe Bougère I'm sorry to hear that you lost some time on this one. We usually don't add bugs to the docs since this would require rework when they are fixed. We add them to our JIRA system, community thread or knowledge base articles. These sources are usually easy to find from google and can be collaboratively…

Hi @SmsParser Bitbucket uses a special YAML file format to represent the pipeline tasks configuration. It does not work like a shell script although it has some similarities. The external file you are trying to call as a script should be in shell format. There are multiple shell types out there like csh, sh, bash etc. This…

Hi @vabard This is not a problem with Pipelines environment, but a bash evaluation issue. You are trying to send variables that are not evaluated to an SSH command. The cat command will send the text inside the test-deploy.sh file. They are not variables until a terminal try to read them. The remote receiving them will not…

You are welcome!

Hi @christok If you remove the -H "Accept: application/json" part it will return the XML you want.

Hi @christok The number of results is set by default to 25. You can change it by using the max-result property when calling the REST API endpoint as Alexey properly shared. e.g. curl -u admin:admin -X GET <BAMBOO_URL>/rest/api/latest/plan/<PLAN-KE Y>/branch?max-result=1000 I see this property is missing in our docs for…

Hi @Maxim Gromov Usually, this type of issue is related to application links communication not working properly which affects the events that should be sent from Bitbucket to Bamboo. What I suggest: * Check if the changes in the old <Bamboo_Install>/conf/server.xml were migrated to the new one. If this configuration…

You are welcome @Manish Kumar!

Hi @Manish Kumar, I built the following example that should speak by itself: definitions: step_def1: &myCommonStep1 name: Step1 name script: - echo "command 1" - echo "command 2" step_def2: &myCommonStep2 name: Step2 name script: - echo "command 3" - echo "command 4" pipelines: default: - parallel: - step: *myCommonStep1 -…

Hi @Aaron Bauman I hope that this example can help you to reproduce the configuration: definitions: step: &myCommonStep script: - echo "command 1" - echo "command 2" pipelines: pull-requests: '**': - step: *myCommonStep branches: master: - step: *myCommonStep default: - step: script: - echo "command 3" - echo "command 4"…

Hi @François Guillot, As far as I can tell we can't get that from variables. I have a different suggestion for you. Get the plan key (it could be from a variable) and use a REST API: curl -u admin:admin -H 'Accept: application/json' \ -X GET <BAMBOO-SERVER_URL>/rest/api/latest/search/jobs/<PLAN-KEY> \ | jq -r…

Hi @Sarath Sasi You will need to configure your plan with a script task to checkout the SVN repository and commit the content copied from GIT. The commit task available in Bamboo is not able to commit code in SVN, only in: * Bitbucket Cloud * Bitbucket Server / Stash * Git * Mercurial The alternative you have is to use a…

Hi @Tomasz Kosinski Can you share more details on how this is configured for you? Are you using and extra plugin or REST API for this?

Hi @Tomasz Kosinski, This does not sound like an out of the box configuration between the two servers. In order to help us to understand what is causing this behavior, can you please share with us: * Are you using Jira Server or Cloud? * What is the Bamboo version you are running? * When did this configuration stop…

No, you are not doing something wrong. Thank you for voting and you are welcome!

Hi @Kevin Matlock I believe that the main issue is the fact that specs builds are shown as build results. It, therefore, leads developers to think that a new configuration was applied to those plans and also creating clutter to build results. The fix would require removing the specs results from the build results section.…

Hi @Poojatr Can you share a small example that I could reproduce locally to understand what is happening?

Hey @James Parsons Bamboo agents have two different protocols/channels when talking to the server. Firstly they talk to Bamboo through HTTP to ask about the broker details. Then when they have the broker configuration they try to connect using JMS through the address provided by the Bamboo server. Bamboo knows there is a…