Daniel Santos_157bm4 Atlassian Team

Hi @Ryan Schwoerer * git version - I have 2.22 installed already. Its a bit unclear which versions Bamboo supports. I know the last time I updated Bamboo it did not support the absolute latest git version. Yes, we need to improve this in our documents. We have a feature request for this at [BAM-20511] Update supported git…

Yes, this bug was reported in different comment above, but the link redirect was affected due to a recent change in our issue system. Thank you for adding the new link here.

You are always welcome @Patrick Peace!

Hello @Patrick Peace The behavior you see is expected. You defined two different stages, each stage has a different job. Each job will run in a fresh Docker container. To avoid the issue you are facing you could: Option 1 * Put all the tasks in the same stage. Option 2 * Build a new image with all the dependencies you need…

You are welcome @Adrian Garay!

Hey @Ray Lee There is a plugin you can use to achieve this goal. It is called Conditional tasks for Bamboo. There is a brief explanation about it in this thread: * Solved: How we can configure job with conditional tasks for Bamboo plugin? In your case, you want to run the task for develop but not for uat. This would be the…

Hi @Mike Mintz Take your time to check those repositories and if that didn't solve the issue, just share with us here. =]

Hi @Mike Mintz The error you see seems to be related to the source repository configuration set for your Bamboo plan. When you created the plan, I suppose you configured a repository for it and I think that is the data structure reporting this error. Steps to find the source repository information I'm talking about: *…

Hi @vpandey6 Pipelines was designed to group the output of commands in those expanders. There is no configuration to avoid printing the command itself. This is a way to identify what is the command running from bitbucket-pipelines.yml file. Possible approaches that may meet part of your needs: * Use a variable with the…

Hi @Mike Mintz Instead of going deeper to try understanding what could be the source of this issue, I have a different suggestion that may save time. * Is it a problem for you to remove the repository configuration and add it back? It is possible that recreating them will fix the data structure that seems to be…

Hi @Sreekanth Reddy Seelam I'm afraid that Bamboo is not able to process the passwords stored in your mail server configuration and therefore you will need to recreate it. There is a knowledge base article about this: After upgrading, Bamboo stop sending emails and throws 'Unknown encrypted data format' exception -…

Hi @Sree Kalyani Bamboo does not have a feature for this out of the box, but I shared a workaround in a different thread that seems to be applicable here. Please check: Send email notifications to list generate list generated by job - Atlassian Community. The command mentioned there is mutt and it supports attachments,…

Hi @Poojatr The logging levels for builds are hardcoded in Bamboo. The global log settings configuration (Admin >> Overview >> Log settings) will also affect the build results, but they cannot be configured just for a specific plan. Some of the build results are parsed from server logs which are affected by the global…

Hey @Parth Padhiyar You are always welcome!!! I'm glad that the issue is now solved =] I hope you enjoy Bamboo now that you can use it.

Hi @Tim Finch The following query should help you with this: SELECT L.NAME , B.FULL_KEY , BR.BUILD_NUMBER , BR.BUILD_STATE FROM LABEL L JOIN BUILDRESULTSUMMARY_LABEL BRL ON BRL.LABEL_ID=L.LABEL_ID JOIN BUILD B ON B.BUILD_ID=BRL.BUILD_ID LEFT JOIN BUILDRESULTSUMMARY BR ON BR.BUILDRESULTSUMMARY_ID=BRL.BUILDRESULTSUMMARY_ID…

Hi @James Parsons I'm not able to tell you what is causing this issue only by checking the logs you shared. I'll need your help to provide me with some extra details. This is what I would check if experiencing a similar issue: * How the agent was installed? If you did clone a different agent installation it could make two…

Hi @Parth Padhiyar It seems that the problem you are facing is caused by the wrong JAVA version referenced by the Bamboo process. Bamboo 6.9.2 only supports JAVA 1.8 as per Supported platforms - Atlassian Documentation. You can have other versions of JAVA in your server, but Bamboo should use the 1.8 to start your Bamboo…

That is Great to hear! I'll mark the answer as accepted in this case. Have a good one!

Hi @oswald_zink Assuming you are referring to Bitbucket Cloud, that is expected. We use a range of IPs, which means your communication may happen with any of the IPs described in What are the Bitbucket Cloud IP addresses I should use to configure my corporate firewall?. I hope that helps to clarify the issue.

Hi @Emmanuel Nzekwe The Atlassian product Atlassian provides is Bitbucket. Can you clarify if you are talking about https://github.com/gitbucket/gitbucket ? In Bitbucket, if it is an existing repository, you could: * Clone your Bitbucket repository in the local machine * Copy your files to the repository * Add the files to…

Hi Ryan, Thank you for all those details (they are really important) and I'm sorry for the late response. You should always prefer Bitbucket server trigger over the Polling trigger. The polling trigger will create more work for Bamboo and therefore more git processes running in parallel over time which could be one of the…

Hi @WET It seems a rather complex implementation for a case that doesn't look common. Could it be just an option (like a checkbox) where we can avoid the merge if the build was triggered manually or by a parent (that was also triggered manually)? My intention is to add a feature request that has more chances to be…

Hi @Ray Lee, You should have the artifact in the build working directory, by following the first configuration shared. Builds can be run in local agents (in the Bamboo server) or in Remote agents (can be anywhere in the same network). Assuming your Eclipse workspace is in the Bamboo server, you can use a script task to…

Hi @Subhi Andrews yes, you can use the Build monitoring feature, but that will consider the whole build time and will not work on local agents. If you use remote agents that should work fine. =]

It's a separat repository. This sounds like the only option, which isn't pretty at all. I agree this is not a pretty solution, but I don't see a better option now. We have this old (and not very popular, low votes) to create a merge task for git. [BAM-11552] Task for merging between git branches. It should be an option to…

Hi @Ray Lee I'm not sure if I understood you correctly. * Are you trying to download the artifact from the parent plan (plan A) or from and external source from outside Bamboo?

Hi @Subhi Andrews I'll make some assumptions here: You are running the build in a Unix-like remote agent You are running the Ansible Playbook command from a script task. Possible solution * Use the command timeout to define the maximum time you think the Ansible Playbook could take and still succeed. * Add the option set…

Hi @WET I think I'll need more details to really understand what is plan2 doing in this case. * Is plan2 using the same repositories of plan1? If plan2 is using different repositories, the best course of action seems to be using a script task for this merge and running the checkout/merge commands there. The problem here is…

Hello @daneshrao I'll need to get a little bit more details to request our developers to check this. * Can you share what is the event message you have? Any extra details will help us to address this better.

Hi @Operations KodegearTech It is a little bit hard to understand what is causing this issue of yours without understanding your deployment process. I'll need to ask you some questions in order to check where this issue could be located: * Are you using Bitbucket server of cloud? * What makes you think the issue is located…