Daniel Santos_157bm4 Atlassian Team

Some useful questions to more forward: * Just to make sure, have you added the public certificate or the private one? (you need the public in Bamboo) * Are you using GIT as a capability? * Are you calling git commands from a script task? * Is git working at the terminal, from outside Bamboo? * Have you tried the git…

Hi @sangeetha, If you want to create a variable with data that is generated during the build, that is the way we do it. Can you elaborate more on what you are trying to achieve? We might be able to find a different path to solve your demand without creating the metadata.

Hi Jules, Let me share a header we have in Bamboo on plan and global variables pages, which might explain why this is failing: For task configuration fields, use the syntax ${bamboo.myvariablename}. Bamboo also supports nested variables. For instance, if you set variableName = world, and variable.value = Hello…

Hello Adrian, * Have you added the SSH key at Cog >> Overview >> Shared credentials? * Can you share where you are trying to use the SSH key, in what task?

Hi Terry, I suggest you using Bamboo Java repository specs. This is how you can create a plan with this feature: Tutorial: Bamboo Java Specs stored in Bitbucket Server - Atlassian Documentation. Once you have a plan in this format you should be able to change the file pattern by performing commits into the plan…

Hi @omerozsakarya, Global variables will affect the entire instance and because of this you need to have admin permissions. There are two types of global admin permissions (Bamboo permissions - Atlassian Documentation): * Admin * Restricted Admin Any of those will give you the ability to create Global Variables.

Hello. Usually this problem happens when there is no agent to process the specified build. Since this problem is happening with multiple plans I would try: * Check if your agents are available. * If they are online, verify if they are dedicated. It could prevent other plans from using it. * If this is a problem with GIT,…

Hello Nelson, You will need to add the public certificate in Bamboo if you didn't do it yet and add the reference to cacerts in the git configuration. The same problem is described here: Unable to clone Git repository due to self signed certificate - Atlassian Documentation. This document is for Fisheye, but the same…

Hi Sravani, Are you able to see the full docker in the build logs? Is there any caused by stack trace there that you could share? Is docker installed in the Bamboo server? Is just this docker task failing or all of them?

Hi Rafael, I'm assuming you are talking about the min and max heap, so I'll give you my answer to that. This is the page we usually recommend: Bamboo Best Practice - System Requirements - Atlassian Documentation. The page talks about the general server specification. We usually define the min heap equals to the max heap to…

Hi Rajeev, This usually happens when you don't have the admin rights with the user you are logged in. Possibly something was changed in the user repository or in global permissions. To regain admin control on your instance and be able to fix permissions or even the user repository configuration, please: * Stop Bamboo * Add…

Hi Anthony, This is what I suggest: 1. Try to find messages like this one in your Bamboo logs (<Bamboo_Home>/logs/atlassian-bamboo.log). 2018-10-23 19:44:21,533 INFO [http-nio-8085-exec-6] [com.atlassian.bamboo.filter.AccessLogFilter] 127.0.0.1 POST…

Hey @ishan_walawalkar, Can you share the full URL used including its parameters? The 404 error might happen when the request is malformed. Can you also share what version of Bamboo is this? Are you using Curl for your request as shared above?

Hi Niko, I'm glad to know you already implemented it and thank you so much for writing the article and sharing it here =]

Hi Murphy, The variable bamboo.repository.branch.name is deprecated but the variables bellow (which you already cited) should do the same job. bamboo.planRepository.<position>.branchName bamboo.planRepository.<position>.branch Please keep in mind that those variables will depend on the repository type used and their order,…

Hi Juan, If I understood you correctly the behavior you describe is expected. The view permission will allow you to view any UI screens not related to configuration changes. The details you are trying to see are not designed to be exhibited as read only fields. This happens to be the same for Bamboo plans. Any…

Hello Niko, I have the impression that it can only be achieved in TeamCity when using a snapshot dependency (Using the Build Number of another Configuration – TeamCity Support). I'm not sure if this is the same idea (I don't work with TeamCity), but in Bamboo we have the plan build dependencies (Setting up plan build…

Hey Tim, Can you share with us were this error was observed and the set of steps taken to reproduce it? Possible troubleshooting steps: * Find differences between branches that work and this one. * Clone this branch from outside Bamboo and verify if you will experience any error. * If your repository is not that big, try…

Hello Ryan, It could be a problem not related to the DB configuration as well. This are the troubleshooting steps I probably follow: * Check the server logs Unix like:<Bamboo_Install>/logs/catalina.out Windows :<Bamboo_Install>/logs/bamboo-stdout.<DATE>.log * If the problem is related to the DB, please make sure:* Your…

I know this request is a bit old, but I would like share that this is the right way of doing it. We would need the Bamboo version and the returned error to investigate why it was failing. I just run the same test on 6.6.2 (I know it is pretty new) and it works just fine: curl -u <USER>:<PASSWORD> -X POST…

Hi Adam, I know this question is a bit old, but I think it worths to link relevant information here. This problem could bee solved with the implementation of the following feature request: * [BAM-19825] Branch regular expression filter for automatic PR detection Anyone that thinks this feature is relevant might want to…

Hi Nicholas, It is difficult to know what is happening there since we don't have all the details, but I can share with you what would be my possible troubleshooting steps on this scenario: * Make sure the data is indeed in your development branch. Try to use the Windows or Linux terminal (avoiding Bamboo) to checkout the…

Hi Neculai, Global variables are not accessible from the startup script text field. I'm afraid you won't be able to save/use credentials that way. It seems you need those credentials before the agent comes up, otherwise you could just use a plan variable for that, calling it during build time on a script task. You can…

Hey Alex, Good to know you found something there. I hope that is the only issue with the export =] Take care!

Hey Alex, It took me a while to realise that the class com.atlassian.bamboo.migration.stream.LoginInformationMapper does not exist in bamboo versions after 5.9, this happens to be the same for the loginInfos.xml file (at least for Bamboo 6.6.2). Your export seems to have failed to write values to the loginInfos.xml file…

Hey David, Great to hear! I'm glad you could find what was causing the issue and fix it. \o/

Hi @Anis Ben Romdhane, I don't have knowledge on the Nexus environment but if you think this can be achieved though a sequence of commands or calling an external nexus client or even using REST API, then you should be able to config a Bamboo script task for that.

Hi @Dhiraj_Kumar_Mishra, The following investigation/troubleshooting steps can be useful: Divide and conquer * Where is the problem? ▶︎ What is the behavior in the agent machine to checkout the same repository from terminal? (no Bamboo involvement) ▶︎ If the checkout is slow in the terminal, what happens if we do the same…

Hi Monica, I would start investigating the trigger configuration in the integration build plan. If the repository is the same, you have a trigger configured to build your plan on new changes and you have that plan branch, the integration build plan will run the build. Things to check: * What is the Trigger configured? *…

Hi @arun4d, This configuration can be achieved in a Bamboo Deployment, but it is not automatic. Any environment can run separatedly and build an specific branch configured in your environment trigger. This is what you can do: * Create the env master * Add a trigger (After successful build plan or other) for the master…