Daniel Santos_157bm4 Atlassian Team

Hi @Sinan Köylü, There are multiple ways to do this. It will rather depend on how you want to do it and what are your constraints. Some options I can think: * Your remote windows has an API that can be called to load the deployment results - In this case, you could use a script task to call the API and do what you need. *…

Hi @radhakrishna swamy K, I see you are mentioning those fields with "self." in the beginning. Is this a python code? * Can you share from where those fields are coming from? * Are they database columns?

Hi @Benjamin Wilcox That is not the way Bamboo was designed to work and this is why you will need to do some extra work in order to make it happen. I would try this: * Remove the task download artifact * Add a script instead, with commands to perform these 2 steps:* Find what is the last build from the plan you are trying…

You are welcome!

Thank you @timothy schmidt! It makes sense. Let's see how the system will behave. I hope the problem is solved already. Have a good one!

Good to know! =]

Thank you for sharing. I'm afraid we will need to open a support ticket to investigate this one further. Do you want me to open a support ticket for you or should we wait to check if this problem will happen again? I'm suggesting a support ticket so we can evaluate with more details your server and agent logs. We could…

Hi @timothy schmidt, I saw a case where a build was calling an external tool that was not properly closed after finishing the build. The app was locking a file and it was breaking the next build right at the beginning, in the build working directory task. * Did you try to manually remove the remaining folders when this…

Hi @Mahesh Pawar, You cannot change the variable bamboo.RELEASE_BUILD_NUMBER from the build itself, you will need to inject a different one. Injecting a variable will require a different namespace right after bamboo, e.g. bamboo.<NAME_SPACE>.<VARIABLE> .The namespace can be defined in the inject task. It doesn't need to be…

Hi @jlu, * What is the Bamboo version affected? * Is this happening to other plans or just this one? * Was this project created through specs? * Can you share what is configured in Admin >> Global Permissions and the Project permissions for the affected user? I'm just trying to get enough information to try reproducing…

Hi @timothy schmidt, The document that you should do as a reference is: Supported platforms - Atlassian Documentation. At Java >> Good to know you will see: * You only need to run the agent and server using a supported JDK. Agents can build software with any JDK version. Bamboo 6.7.X requires Java 1.8 for both agent and…

Hi @Josel Joaquin, Those messages just mean that the user browser is constantly checking the Bamboo server for build status of the plan QEBSD-BEBPC. It means the user has browser tab with some page from plan QEBSD-BEBPC open for a while. There is nothing alarming there.

Can you check if this variable (BAMBOO_ANDROID_HOME) is declared in your plan and/or if it shows up in your build logs? Do you mind also trying to add the sdk.dir as follows? <span>sdk</span><span>.</span><span>dir </span><span>=</span><span> C</span><span>:</span><span>/path/to/sdk</span> or even using backslashes, but in…

Considering this is Bitbucket pipelines than you will need to migrate your plans manually, sorry. There is no feature for this.

Bamboo 5.7.2 uses application links version 4.1 and Bitbucket 5.12 uses 5.4.4. Aplication links version 4.1 are not compatible with 5.x ones. For this reason some funcionalites relying on application links may not work properly. Some of the features are: * Triggering build events * New Bitbucket repository configuration in…

Hi @linu joseph, When you say cloud Bamboo, were you referring to Bitbucket pipelines? Or is it a Bamboo server hosted outside of your company? Atlassian deprecated Bamboo cloud instances a long time ago, this is why I'm kind of confused with your statement. Anyway, there is no automatic way to migrate plans from one…

Hi @[deleted], Have you tried changing ${bamboo.ANDROID_HOME} to %BAMBOO_ANDROID_HOME% The second variable format is the one we use in Windows. Could you try that and share the results you get?

community Hi Sibi, I got that you want to trigger a build based on multiple repository changes, but I still need to understand what exactly conditions you want to be met for a trigger to happen in Bamboo. * Do you want X commits then a build triggered? * Do you want a build only when a specific repository (the main repo)…

Hi @Matt Armstrong, Bamboo does not have this type of report. What think you could do is: * Parsing the build results to extract any information you need from the agents that is available in the build log * Use the following query to get the agent name and hostname|ip from the Bamboo DB:SELECT BR.BUILD_KEY PLAN_JOB ,…

Let me highlight 2 points that in my opinion usually need more attention: * Windows environment variables will rely on the parent process environment and on what user is running the current process. This means that you always have to make sure the Bamboo agent running your build has the variables you need to properly run…

Hi @[deleted], * Can you share in what task you are running setting the below command?set ANDROID_HOME = $(bamboo.ANDROID_HOME) gradlew writeProjectInfo I'm asking that because there is a mix between Windows and Linux way of treating variables. Windows variables should be evaluated like:%BAMBOO_<MY_VAR>% so on a windows…

Hi @Дмитрий Дымский, The timeout check is hardcoded to 60 seconds. Can you share with us if you are experiencing a timeout bigger than that?

You are mostly welcome @Ivan Hu!

You are welcome mostly @DPool!

Hi @Brian Mansfield, I was searching for that error No names found, cannot describe anything. and found that could be related to a shallow clone configuration in repository configuration. Do you mind checking the repository configuration for this plan and making sure you have the option [ ]Use shallow clones unchecked?…

Hi @Ivan Hu, I was studying this problem and running some tests and I can confirm that this issue is caused by [BAM-17819] Deployment Release artifact list not updated when the build plan second stage finish. To avoid this issue you should only automatically trigger the deployment one time per build plan and in that moment…

Do you see any new error in the logs? Have you tried to access the instance though its direct IP to avoid any proxy issue?

Hi @DPool, We have very few cases with a similar error and they were related to a misleading configuration file (that could be either missing or corrupted). Do you mind checking if the file <Bamboo_Home>\xml-data\configuration\administration.xml is there and if it has content inside? This would be default content for a…

Hi @timothy schmidt, That KB was designed to HSQL DB which was the old version of Bamboo embedded DB. As you may know, this database is not very safe, bing more susceptible to corruption in case of hardware or software instabilities. Newer versions of Bamboo are using H2 which should be more reliable then HSQL but still an…

Hi Chris, The configuration you want would require a feature that should trigger a Bamboo build based on an event coming from a Crucible code review completion. Crucible is not capable of doing this out of the box. We have an old post about this that is still valid: Crucible - Upon Review Completion. Bamboo can be easily…