Daniel Santos_157bm4 Atlassian Team

Hi Julius, You will need to create a deployment project for each of your clients. We don't have a mechanism in Bamboo to process that stratification at the moment. I've opened the following feature request to contemplate your need for this feature: * [BAM-20670] Multi tenant/client deployment support Let me know if you…

Hi @Mikko Sartanen I hope you are talking about a Bamboo build running on Linux. Assuming that is the case, please consider the following JSON content as an example: {"menu": { "id": "file", "value": "File", "popup": { "menuitem": [ {"value": "New", "onclick": "CreateNewDoc()"}, {"value": "Open", "onclick": "OpenDoc()"},…

Hi @schow-lmi3d That is really strange. Bamboo should see exactly what is stored in the remote git repo. * Is it possible that the tags update was not transferred to the remote?git push --follow-tags * What happens if clone this repository again and try to checkout for that tag, will that work as expected? * Have you tried…

Hi @Vivien Jovet No I can't do that unless I leave a dead branch at all time. The `Branches` plan I've shown above is meant for feature and bugfix branches, so once they're merged into the develop branch, they are deleted. Got it! Thank you for explaining it. Does Bamboo have a REST API endpoint to disable a plan? If it…

You are welcome! Thank you for voting on that feature request. Have a good one!

Hi @David Gard Things I would try to move forward: * Create a new plan and new deployment for this plan. Add the trigger and check if this will fail as well. This will allow us to see if this issue is only present in the build/deployment you already have. * Reproduce the problem and share the logs:* Run the build * Check…

That is great, you are welcome!

Hi @Vivien Jovet I've opened a bug for this behavior, it seems incoherent to me and can confuse users: * [BAM-20669] Setting a plan as disabled prevents specs of publishing its configuration I was thinking about your initial issue and it seems simpler just to publish this plan with a different main repository. Instead of…

Hi @Sascha Mowtschan I've created the following feature request for this: * [BCLOUD-19512] Add conditions to run a pipeline step Please vote on this one and add yourself as a watcher to make sure you will have any updates from that ticket. Let me know if you have more comments or questions on this matter. =]

Hi @Miguel Vargas We don't have this type of configuration. The best you can do is to set an environment trigger that will run the environment when a successful run of another environment happens. In other words, you could automatically have: * Build plan triggers Env1 * Env1 triggers Env2 * Someone from one team manually…

Hi @Simon Hooper You are correct, after some tests, I realized that we don't have a variable to provide such information directly. I've created a feature request to add a new variable for this: * [BAM-20668] Variable to get plan branch name - Create and track feature requests for Atlassian products. We only have a partial…

Hi @Vivien Jovet Yes, you need the remote trigger configured in the main plan, but you can disable that one and therefore it will not be triggered. Please add your Remote trigger back and disable the main plan by going to: * Plan configuration >> Plan details and uncheck the [ ]Plan enabled checkbox. I hope that will give…

Hi @Miguel Vargas I'm not sure if I would give you a better response than the one given by @Jobin Kuruvilla [Adaptavist] in this thread: https://community.atlassian.com/t5/Bamboo-questions/How-do-I-configure-a-deployment-to-pause-and-ask-for-a-user/qaq-p/816388. Please check that thread and if you still have things to…

Hi @craigwillis-a12 I was about to create a support ticket for you to allow us troubleshooting your repository, but I noticed you already did that. Let's follow the investigation with our support team and if the fix can bring benefits to other users we can share our findings here. Thank you for opening the support ticket.…

Hi @Sascha Mowtschan We don't have such configuration to set special conditions for a build to happen. Would you mind sharing what type of conditions you would test in the when clause? Depending on what you share for those conditions I'll be able to open a feature request for this. If you are attempting to avoid builds on…

You are welcome! =]

Hi @Anton_Kuryan we don't have any mechanism in Bamboo to can prevent that. I was trying to find a way to solve this problem and the best I could think of was somehow failing the final deployment when the results of Env1 and Env2 are still not available. We don't have such restrictions or dependence between environments. *…

Hi @Romit Bhandari In order to investigate this issue we will need to have access to your Bitbucket account and that will require a support ticket. I've created a ticket on your behalf. Soon you should receive an email with its details. I kindly ask you to take your time and share your findings here when the problem is…

Hi @Enrique Fernández-Polo Puertas Thank you for flagging that. The example in that document page is incomplete. You should use something like: curl -u <USER>:<APP_PASSWORD> \ -X POST https://api.bitbucket.org/2.0/repositories/<USER>/<SLUG>/src \ -F <REPO_FILE_NAME>=@"<LOCAL_PATH_TO_FILE>/<FILE_NAME>" e.g. curl -u…

Hi @GK Good to know you discovered it was a plugin feature. Unfortunately, this plugin is not anymore available. It was designed by a company called CalmWare which does not seem to have updated it for newer versions of Bitbucket. I was not even able to find the plugin information in our market place. It was a free plugin,…

Hi @GK Just from your description, it is difficult to identify where the Tags link was located (or in which page/location you miss it). Are you talking about this one?

Hi @David Gard According to your description, the build deployment should be triggered after the build. Would you mind double-checking the plan and selected branch by going to Deployment configuration >> Edit build plan >> Linked build? Other checks to help troubleshooting this: * Do you have other plans where a similar…

Hi @Mohammad Faizan I suppose it is possible to do this if you customize the instance by write your own plugin. The best channel to get some tips on this direction is https://community.developer.atlassian.com/. There you will find either Atlassian and Community developers that can share their experience with you.

I got it! You are on the right track. If your remote agent is not able to reach the server there is no deal. Let's wait for their feedback.

Hi @joshysav Is docker runner working with other docker images? Would you mind checking this? We might be facing a different issue and isolating the problem will help us to understand what is causing it. It would be even better if we can reproduce it.

Hi @Дмитрий According to your description, the feature you need is Smart Mirroring for Bitbucket Cloud. Please check the page and let us know if that is what you need. We have another document that should help you to clarify how this feature works: * Set up Bitbucket Smart Mirroring - Atlassian Documentation

Hi @Nikhil Kumar All the content from xml-data/build-dir can be removed if there is no build running there. This is the data stored there: * Build files created during the build, along with a local copy of the latest changes of the affected source repositories * Agent cache for each source repository that eventually was…

Hi @Staffan Bäcklin Thank you for rasing the flag about this confusing information. I suppose you saw it on this page: https://www.atlassian.com/licensing/bamboo. After reading your message and digging a bit I found that page with a table on section 7 which has the wrong information. I reported this internally and soon we…

Hi @James Brown The agent identification/authorization is processed based on UUID and IP address. * Do you mind checking if your Bamboo server or agent changed the IP while the server was restarted?

Hi @Swatilekha Paul In order to identify what is causing this, we will need to check in which conditions this problem is happening. Please help me with the following questions: * Do you have other specs plan running as expected? * Was this plan working before from specs? * Is there any recent configuration change/plugin…