Daniel Santos_157bm4 Atlassian Team

Hi @Shawn Sesna Thank you very much for the clear enlightening examples. Bamboo has a similar configuration for release versioning. The build number for Bamboo is just a number from 0 to max(int). What defines a given build is the PROJ-PLAN(or plan branch) + scalar (build number). A given build can be promoted to a release…

Hi @Mohammad Saleem The command above is not running possibly because the PATH variable is not defined while the command is called. It usually happens when the agent is not running with a Linux local user, but instead with a system user. We do recommend that a local user is used and if this is your case, you can adjust…

Hello Guys, I just updated the link shared with a new one!

Hello @mduduzi ndlanzi This is strange, it shouldn't be there! * Can you share the set of steps you use for this installation? * Is this a clean installation (with no prior data) OR are you installing and migrating content from another server? * Are you following the steps described in this document?* Installing Bamboo on…

Hi @Shawn Sesna I'll need your help to make sure we are on the same page. When I read the title of your post, I think about the Bamboo number which describes each build. It is the number at the end of a build key: e.g. PROJ-PLAN-76 (build 76). Some times we need to reset this number to meed the project needs. We may need…

Hi @poovaraj I'll contact you through your personal email to investigate this issue further. Thanks for raising this here!

Yep, like @Jimmy Seddon said! Thank you Jimmy!

Hi @Michael Thank you for raising this question. Global, plan and deployment variables can be evaluated in tasks by using the following format: ${bamboo.<variableName>} Please notice that this evaluation takes place before the task is executed. Let's suppose you are adding the following line in your inline script:…

Hello there! I was able to find another case in our support system with similar behavior. There is a problem with the AuditLogSaveThread in handling some exceptions (e.g. DB persisting issues). The thread may die silently leaving the Bamboo server up and running without the audit support. This problem was reported in this…

Hi @shivaram From what I can understand, the issue you are facing could be caused by networking misconfiguration issues. I'll try to share what I know in the hopes that it will help you move forward with this configuration. * The agent is the one trying to connect with the Bamboo Server, not the opposite. It will know…

Hi @cdsb, I understand your point, yes, that approach is not considering pull requests from multiple branches coming from a forked repo. My suggestion was an attempt to minimize the effect of this design in your workflow. Somehow I forgot to mention the feature request we have to improve this behavior: * [BCLOUD-13162]…

Hi @Charlie Jonas That is not possible through bitbucket-pipelines.yml default coding. What you could do instead is to create a script with the command you want to run and call that script in multiple steps. There is a feature request that might address your request: * [BCLOUD-17181] Allow users to define tasks / step…

Hi @Sujit Kumar Sorry, your response flew under my radar. There are multiple ways to implement CD in Bamboo. I think the question is how do you want your CD to work. What tests/validations you need to run before to make sure you can deliver your app/changes to staging or production. You could use a building plan for that…

Hi @Sebastian Montoya This is odd. If I had to troubleshoot it I would: * Check if the Pipelines feature is enabled. Repository settings >> Pipelines - Settings >> Enable * Check if the webhooks are configured and are able to see the pushes for the branch specified. More details in section Checking Webhooks. * Check if the…

Hi @poovaraj Let me try to answer your questions. How to run more than one job in single machine concurrently using single agent? This is not possible, not using a single agent. You need as many agents available as the number of jobs you want to run in parallel. Bamboo has two types of agents: * Local agents* They are…

Hi @MuruganSankar It would be great if you could share the build log errors right before this one. They would probably help us to see what could be causing this one. I'm assuming this is working on terminal, but not in Bamboo. Is that correct? Please keep in mind that after changing/adding environment variables you need to…

Hi @JacekP We don't have a feature for that in Bamboo, but you can use the following DB query to search for plan jobs configured to use the given plugin as a task. SELECT full_key, xml_definition_data FROM build b JOIN build_definition bd ON b.build_id=bd.build_id WHERE xml_definition_data LIKE '%<PLUGIN_KEY>%' (i) If you…

Hi @[deleted], If I understood you correctly, you are trying to configure a capability that will be installed during a build and you don't know the path of it before its installation. Can you confirm that? If this is the case, the only solution I can think of right now is: * Set the custom capability path with a fixed…

Hi @mduduzi ndlanzi There is something really odd going on there. I can see that your paths are mixed with Linux and Windows formats... e.g.: /opt/bamboo/atlassian-bamboo-6.9.1/bin/C:/bamboo/bamboo-home/xml-data/build-dir/DS-DBR0-JOB1 Questions * Where is the git repository located and how is it configured in Bamboo? * Was…

Hi @Mj You are most likely to get a good response to this question if you submit it in https://community.developer.atlassian.com. That is the right channel for discussions around Atlassian API and development. Please create another question there and add the relevant tags =] I hope you get an answer to your inquiry soon.

Hi @Hyd3k I asked @Rafael Pinto Sperafico (a community leader) with more knowledge in this area to help with this one. I'm glad that he found some time to share his wisdom with us. I hope it helps.

Hi @schow-lmi3d I can see the problem is happening when publishing the artifact. I'm not really sure if the clover plugin is the only source for this issue. I have some questions that would help us to investigate this scenario further: * Have you had the opportunity to check the logs to see what stack traces are showing up…

I'm very glad to hear that @Roozbeh Shafiee! Better when no pain and blood is involved =] Keep rocking out there! Have a good one mate!

Hi @Pankaj Malhotra If you are talking about the tasks provided by Artifactory for Bamboo | Atlassian Marketplace, you will only be able to use them in JAVA specs. YAML specs do not have the ability to configure those tasks. As you mentioned (...or we need to use curl?), you will need to run your calls using a script task…

Hi @Lei P I saw you opened a ticket with our support team for this issue and it was already resolved. I'm adding the findings here in case other users face the same issue. Problem This problem may happen eventually. The issue is caused by the following bug which was fixed in Bamboo 6.9.0: * [BAM-19945] Elastic Bamboo -…

Hello @Arun I personally don't have enough knowledge about MSBI SSAS 2012 cube, but considering you need to use MSBUILD and Microsoft.AnalysisServices.Deployment command, these are the options I see you can use: * MSBuild - Atlassian Documentation Bamboo has a MSBUILD task that serves as a wrapper of the MSBUILD command…

Hi @Karol Urbaniak Thank for your question and for sharing all those details. Is it reasonable to create such environment? Yes, for sure. What is not clear is where are your doubts. What would you do differently? If so, what aspects are you considering? Some comments on what you shared: * You will run Bamboo on Linux ✔︎ I…

Hey @Ricardo Alan Rodriguez Soto Good to know that you are working with @Reynaldo Cruz Pérez in this one, * Did any of you find log messages that indicated Crowd as the source of the issue? The file <bamboo-home>/xml-data/configuration/crowd.properties should have the Crowd URL and credentials that Bamboo is using (or…

Hi @Sergio Walter Ruz I think it was not clear since the beginning that you were trying to use different branches in the same deployment project. A deployment plan is associated with only one plan and just one branch can be configured at each time. In other words, you can deploy from multiple branches, but you will need to…

Hi @rupakchapa39 To troubleshoot this error better you will need to check the log messages in this file: * <bamboo-home>/logs/atlassian-bamboo.log Please check if there are other messages also associated with this error. It is very common that incomplete proxy settings will cause this effect. There is a document covering…