Jeyanthan I Atlassian Team

may i have the contact administrator You may. I showed you the way to reach them :) Please note that this is a public community and we have no control over your internal infrastructure. Cheers, Jey

You will have to contact your administrator for further assistance on this. Click on Contact Administrators link that you see at the bottom in the footer section to get their details. Hope that helps. Cheers, Jey

Hey Deepak, If you chose GitHub as the repository host, you will not be able to choose SSH type for authentication. You are allowed to authenticate via HTTP(S) using Personal Access Token only as described on this page. Hope that helps. Cheers, Jey

I assume this is the news link you are referring to - https://www.gitkraken.com/blog/2021-github-authentication-policy-change. If so, it appears that authentication via GirKraken or similar Git clients is affected. If they have been relying on a username and password to connect GitHub, It's time for them to transition to…

Hi Deepak, I remember GitHub has already deprecated password authentication to their APIs last year as per Deprecated APIs and authentication - GitHub Developer Guide, Since then, we can only use your Personal Access Token (PAT) in place of password in your linked repository of type GitHub repository. This anyway doesn't…

Hey Irshad, The snippet you shared appears to have only access log entries. I'm confident that you can find the reason if you scroll up further and spot entries just before this access log. That being said, just so you know, this ticket has landed in a community forum and thus any response you get here happens on a…

Hey Irshad, I see that you are installing Bamboo 6.5 (which is pretty old). To check what is happening in the background, you would have to look at /bamboo-install/logs/catalina.out file.

Hey Bjorn, Just wanted to close the loop after our internal discussion. A bug report - BAM-21327 has been raised for this and is fixed in the next major release - Bamboo 8.0 already. Thanks again for taking the time to flag this. Cheers, Jey

Ah, right. My apologies. I just raised an internal ticket to follow up on this further. Cheers, Jey

Hi Bjorn, We'd need to review appropriate logs and understand what happened. Do you mind raising a support ticket with us and share the agent log and server log captured during this timeframe? Cheers, Jey

Hi Rafer, I agree that the binaries to download are not in order. Just so you know, when you see 6.5 in the upgrade docs, it is okay (in fact encouraged) to choose the latest version of that. So, in this case, 6.5.1 is the latest minor version in 6.5 release and you may use that binary to do the upgrade. Hope that helps.…

Just in case if anyone lands on this page, starting from Bamboo 7.2 onwards, one can choose 'Tag trigger' based on new tags pushed. This is explained in this page - https://confluence.atlassian.com/bamboo/tag-triggering-1031180298.html Cheers, Jey

Further to our discussion internally, just to close the loop, processing_duration seems to be the value that Bamboo shows on the user interface as duration but I'm not sure. You are right. processing_duration column is the one you see in the build result summary page in Bamboo UI. My purpose is to find out how many hours…

Hi Bhumika, From your screenshot, I see you have copy-pasted my command literally without modifying it with your username and the respective Git repository. Please contact your administrator for any assistance with running the respective command via command prompt. Cheers, Jey

Hi Bhumika, have you got a chance to try what I requested above? What happens when you try to clone on your server via a command prompt outside Bamboo? Also, your logs/atlassian-bamboo.log should hint what the problem is. It could sometimes be that the particular user as which Bamboo is running might not have access to a…

Hi Bhumika, From the limited information you shared, I understand you have issues with cloning a Git repository using "Source code checkout" task. To verify if the issue is specific to Bamboo only, could you please run the below command with the same credentials configured in Bamboo and see if it works? This is to see if…

Just to close the loop, this has already been fixed in Bamboo 7.1.3 and above.

Hi @yogesh_devi , Of course, you can have agents and server on different networks. Bamboo server and agents need 2 ports to talk to each other. I can share the ports that need to be opened for it to work fine and you can decide how to configure in your setup. * Port of the Bamboo itself: 8085 by default and when no proxy…

Just in case if anyone landed in this thread via search engines, we created a dedicated page that explains these scenarios in detail along with a query that you can run to list those Bamboo jobs that are counted for license restrictions. * Bamboo Starter License - Checking number of Bamboo jobs for license restrictions…

Hi Stef, Thanks for bringing this up. I believe you are referring to the below section in the FAQ page. DO PLAN BRANCHES COUNT AS JOBS? Yes. The use of the Plan Branches feature has a multiplicative effect on the number of jobs configured, and therefore, an effect on the 10-job cap. For example, a plan with two jobs that…

Hi @doug.curtis, It looks like you have stumbled onto this bug. * bouncycastle throw NPE after upgrade to java 8 u272. linux agent fails to connect or UI won't load with ERR_SSL_PROTOCOL_ERROR Glad to see that you managed to fix it by downgrading Java. If this was not an option, I was going to suggest the workaround…

Hi Rahul. If you trigger a plan build manually, you can override any global variables or plan variables with your own parameters when triggering a build manually. This is explained in this page. Hope that helps. Cheers, Jey

For some reason, 54663 is not accessible from the agent. Although 8085 is accessible. You'd need to work with your network admins to make this port accessible from the agent. I'm confident that you can see the agent loading on the server once 54663 is accessible. Cheers, Jey

Hi @Jack , Bamboo server and agents need 2 ports to talk to each other. * Port of the Bamboo itself: 8085 by default and when no proxy is used * Port of the broker: 54663 by default. You'll find the full broker URL in the Bamboo admin panel (System -> General Configuration) The traffic between agent and server is…

Great! Have you also gone through the logs that I proposed? Did it give a hint? Cheers, Jey

Hi @runnerpaul , The exception Could not create file: c:\Program Files\Bamboo\temp\jarFromResource4243020160613851350.jar denotes that the user as which you are running Bamboo doesn't have permission to write to the temp directory. We usually see these problems when you start Bamboo with different user (therefore different…

Hi Team, To move Bamboo to a different server, just follow this link: Cloning a Bamboo instance. As this is a very old version, you will need to ensure that the AWS instance meets all the requirements for Bamboo 5.6 mentioned in this archived page: Supported platforms. If this is not met, you encounter issues resulting in…

Hi, Will changing the application link to stash repo suffice for the job to use the new Stash repo? It is not sufficient to recreate the application link. Do we need to individually change the "Repository URL" for all the linked repo? Not necessarily. You can do this directly on the database to perform a bulk update of the…

Hi Bruce, If you can run this project from a command prompt, you can use Script task to automate this in Bamboo and configure the plan as usual (like explained here). There is no dedicated task for Qt projects. Cheers, Jey

Hi @Jörg Lang and @parthiban.selvaraj, It is possible that you might have added this parameter under bin/setenv.sh. If you are starting Bamboo as a service, you will need to configure either via the command line or in the Windows registry as explained in this page and restart the server. Hope that helps. Cheers, Jey