Daniel Santos_157bm4 Atlassian Team

Hi @John I was able to follow your description and reproduce this scenario. Thank you for sharing a detailed description of the issue. It is indeed a bug. Our issue tracker already has a bug report for this problem as you can see below: * [JSWCLOUD-16754] Bamboo Deployment Workflow Triggers Do Not Function I was thinking…

You are welcome! I'm glad to see that you can now move forward.

I was interested in the Bamboo Server version. It would be something like 6.7.2 or 6.8.0... I'm glad it worked. I'm afraid this task is only accepting a relative path for that field.

Hi @Subhi Andrews Based on my understanding of your requirement I've opened a feature request to allow manually running environments without triggering cascaded ones: * [BAM-20358] Ability to run a deployment manually without triggering cascaded ones These solutions won't work. Wondering if there is a way to commit to a…

Can you share the Bamboo version you are using so I can run another test? Also, could you try using the path below? tests\Arc.We.Tests\TestResults I just want you to run this test with NO working directory variable and the file name which are not needed in this case.

Hi @Ariel R. Conti Most of the tasks in Bamboo have the <bamboo_build_working_directory> path as their default path to work with data. It means that if you don't provide any path, the one used it the working directory. It also means that you can use relative paths. The value to MSTest Test Results File/Directory field…

Hi @prasantk The behavior you are experiencing is indeed expected. Shared capabilities will be inherited by every remote agent available. There is an improvement request to split it into sections specifically to solve a problem that shows up when using multiple OS platforms ([BAM-20114] Shared remote capabilities should…

Hi @Dov Frankel Usually, the task body does not resolve variables from the terminal. The variable ANT_HOME does not exist in the Bamboo application variable context. You should be able to find a variable called bamboo_capability_system_builder_ant_<name> where <name>is the label you gave to your ANT capability when…

Hi @Testing_iesl_co I would read the first message as if Bamboo was not able to see the repository you linked, for some reason. * Are you using Bitbucket server or cloud? * Is your repository configured only in the plan or is it available globally to all Bamboo plans (Linked repository)? The second is not really…

You are welcome @Tim Finch If you don't mind, when you confirm this, please accept the answer as a solution to help other Community users on finding it.

You are welcome! I'm glad there was a workaround that serves to your purpose. See you in the next thread!

I'm glad we could help =] Have a good one!

Thank you for explaining, now it is clear for me what you are trying to solve. I was thinking of what mechanisms you could use to overcome this issue and I didn't find many options: * Use only one dedicated agent for this deployment. This would force the deployment to run just one environment at a time. * Create a chain or…

Hi @kiarashz I suppose the configuration Admin >> Overview >> Concurrent builds is set to a value bigger than 1 in your Bamboo instance, therefore, allowing the same plan to start in multiple agents. If you don't want this setting in your instance you can disable it. If you want this for some of your plans and not for…

Hi @Subhi Andrews I'm not sure if I really got how your plan/deployment configuration is set, but I suppose that if you configure scheduled triggers on those environments you will have what you need. * Can you explain in details how your triggers are configured for this deployment? * Is the plan trigger also triggering any…

Hello Aske, I see you are new here, please be welcome! From Bamboo default notifications you are able to notify: * Users * Group of users (Bamboo groups) * Custom mail (that could be a list, or add multiple entries) * Responsible users * Committers * Watchers If none of the options above works for you, then the option I…

Hi @Matt Martin, Short answer Don't link a Bamboo instance with two different Jira instances. Long answer Although the linking feature works when Bamboo is connected to two Jira instances, this configuration will create confusion for your team. As you already noticed from other threads there are some issues here related to…

Hi @cirosantilli I see you voted in this answer. If that solves your issue, please accept the answer so other users can see this question as resolved and use its knowledge. Thanks!

You are welcome!

I voted on @Marcin Oles question to make the life of other users coming to this question a little easier. Please share your remaining questions on that thread.

As I shared before and @Marcin Oles confirmed in his answer below, you should use the release branches ephemerally. Deploying from a master or any other permanent branch of your choice would solve the issue. So once your release is done you can merge it to a permanent branch and deploy from it.

Hi @Tim Finch Yes, after some deeper investigation. Can you please check if this will address your needs: SELECT DP.NAME, DE.NAME, DR.STARTED_DATE, DR.QUEUED_DATE, DR.EXECUTED_DATE, DR.FINISHED_DATE, DV.NAME, DV.PLAN_BRANCH_NAME, DV.CREATOR_USERNAME, DVIB.* FROM DEPLOYMENT_PROJECT DP JOIN DEPLOYMENT_ENVIRONMENT DE ON…

Hi @cirosantilli Bamboo does not have a feature to filter test results and therefore I just opened one to report your need: [BAM-20346] Implement a test result filter. I worked also on a query as a workaround for this to get the data you need directly from the DB. You should be able to adjust the query to your needs.…

Hi @Frank Sonntag I'm not a docker specialist but there are multiple articles about docker-in-docker out there like this one: Using Docker-in-Docker for your CI or testing environment? Think twice. Can I still turn on Docker capabilities, i.e. run docker from within that container? Yes, you can, but avoiding the Bamboo…

Hi @Simone Chiaretta I'm chatting with a developer about your request and I want to check with you if the feature you think is missing is: * the comparison between deployments of different branches OR * the history of all changes since the branch was created (assuming there is no deployment for that branch before) Can you…

Hi @Purushothaman_Anbazhagan I'm not an expert on Angular, but after some investigation in external forums, I could see that NPM would do most of the work on building Angular apps. Following this approach I think this may help you: Getting started with Node.js and Bamboo. Basically, I see that you would use a source…

Hi @Parth Jeet I installed both in Docker containers to get a better idea of what could possibly be your problem. I suppose the problem is that one or both of the containers are not able to resolve the URL of the other. Do you mind trying this: * Configure both Bamboo and Bitbucket URLs to:…

I'll work on getting someone from Bamboo design to answer this one. The Bamboo devs are located in Gdansk and will only be able to help us tomorrow. In the meantime, I'll share what my understanding is. You may have a release branch where you can run all your builds and iterate over it when testing each new feature added,…

Hi @timothy schmidt Once the cipher key is removed for the first time, the installation is broken. Bamboo has two encryption keys to run the data encryption when necessary, one is in the filesystem and the other one is in the DB. Both are connected and if you remove one the other is useless. Usually, the issues with the…

Hi @Simone Chiaretta This is expected behavior, it happens because the deployment list of contents is created based on a difference between the last deployment and the current one for the same branch. If there is no prior deployment for that branch, Bamboo won't be able to know what commits and tasks are part of that…