Jeyanthan I Atlassian Team

.. and with this REST endpoint, you may construct a curl command like this to trigger a build plan. # Trigger a build of the specific plan curl --user <USER>:<PASSWORD> -H "X-Atlassian-Token:no-check" -X POST <BAMBOO_URL>/bamboo/rest/api/rest/latest/queue/<PROJ-PLAN>

Added to Jimmy's comment, these are picked up from the PATH variable available for the respective user (present at the user and system level) as which the agent is running . So, if you miss something available in capabilities, it must be most likely due to the respective path not available in the user's environment.…

Hey @louwho , To install Bamboo,it is sufficient to have Java 1.8 and the respective version of database installed. Tomcat is installed automatically along with Bamboo. You will need other tools according to your need to run your build (like Maven, Git, etc). This Supported platforms page has more details on the same. If…

Downgrading Bamboo to an older version is not recommended as the upgrade not only alters binaries, but also the database structure and all the dependencies as you mentioned. The best overall course of action would be a system rollback with a snapshot, if available. If not, approaching Atlassian Support for fixing your…

Hey @Amber_Abstract , Git 1.8.5 and later is supported as per the official documentation. Cheers, Jey

The link you have provided is the actual complete documentation reference for YAML. If you are looking for steps to implement this, this tutorial page might come handy - Tutorial: Bamboo Specs YAML stored in Bitbucket Server. Cheers, Jey

Hey @Cdnyoung , Not sure why you cannot post a response. Glad that you were able to resolve the issue and share the steps with the community. Cheers, Jey

Hi As Alexey mentioned, just use the Maven archetype to create a project template as described in the documentation. Note: You must create Bamboo Specs in the bamboo-specs directory, under the repository root. Also, replace 6.x.x with the corresponding version of your Bamboo. mvn archetype:generate -B \…

Hi @Cdnyoung , I'm not familiar with this plugin. Did you get any clue from your atlassian-bamboo.log? Also,Did you get in touch with Zephyr support for this? Cheers, Jey

Hi @Keith Tyler , It is possible that your artifacts are deleted due to your global or plan level expiry settings. You can find in your atlassian-bamboo.log if that's the case. It is also possible that the artifact directory on the Bamboo server doesn't have read permission to the user that runs the bamboo service. Cheers,…

Sure thing. Good luck! Cheers, Jey

Hi @Raju Adluru , For Bamboo to access Bitbucket cloud repository, it is necessary to open the standard ports for HTTP/HTTPS/SSH which are 80/443/22 on the Bamboo server as explained in this documentation. It is not clear what exactly you're doing and where you're getting the mentioned error. If you are getting a 403…

Ah, my bad. Thanks for clarifying, @lukesm01 I can create a new feature request for this. For that, I will need to understand how you would like this feature to work. Currently, plan branches are created based on branches in the repository only and not based on tags. Until then, even if you had an option to choose a Git…

Hey @Konrad Gancarz , If I understand correctly, you wanted to refer the Jira isssue ID in Bamboo builds. I was going to suggest one of the default Bamboo variables for Jira. I then realised there is no variable to collect Issue ID that triggered the build. Available JIRA variables (as of Bamboo 6.10.4) are as follows: *…

Hi @varun.malhotra I guess you are running your build in a Docker container insteadd of running on the agent's environment. Is that right? If so, you may change the build working directory location by navigating to the respective job -> Docker (tab) -> Volumes (section) under ${bamboo.working.directory}. If you are unsure,…

Hi @[deleted] , Usually, all user events are captured in access.log and catalina.out (in Linux based distro only) under <bamboo-install>/log If your intention is to capture user permission changes, Bamboo doesn't track that in the Audit Log. We're tracking this as a bug in BAM-16201: Audit log doesn't record permission…

Hi @Paul O_Brien , It is critical to isolate your Specs repository from users that you do not want them to access. If they have access to Bamboo Specs repository, they can certainly reuse the encrypted variables as you rightly understood. I recommend you to introduce appropriate elevated permission to access this…

Hi Gene, Some followup questions: * Does the user the user have the right permission to access the release? * Is this happening to all the users? * Are there other projects having the same issue? * Did you start facing this after the bamboo upgrade to 6.8.3? * Do you have any deployment related Bamboo plugins installed…

Hey Shyju, I see there is some information in the README file of the respective repository here: https://bitbucket.org/atlassianlabs/bamboo-conditional-tasks/src/master/. Hope that helps. Cheers, Jey

Hi @Muhammad Ammar Abid , If you are running a python file, I assume the script already has an exit statement like exit(). Do you have such entry at the end? This helps to terminate a Python script promptly. Does your ongoing build log suggest something? What happens when you run the same python script outside Bamboo? Does…

Hi @David Meadow As of latest Bamboo 6.10.4, Bamboo supports only Oracle 12c as you see in the Supported platforms page. There are plans to support Oracle 18c and 19c in our future releases. This is being tracked via BAM-20530. Please cast your vote and follow the progress there. Thanks for your patience. Cheers, Jey

Hi @Martin Lukes I see there is an open feature request for the same. Please feel free to upvote and add your use case there. * BAM-13920 Cheers, Jey

Hey @[deleted] , Upon googling, I found SIEM refers to Security information and event management. It's not clear what exactly you're looking for. Could you please elaborate your requirement? I suggest you check the Bamboo audit_log table in the database. That table holds the plans, deployment audit logs and more. Cheers,…

Hey @Catalin What do you see in your build log when the script task is executed? Cheers, Jey

Thanks for clarifying. The latest version definitely has enhanced features and bug fixes. For now, your atlassian-bamboo.log should hint you the reason for trigger failure. You may also use this java property to add verbose output to your log:…

Hi @Carl Davis , Your situation sounds achievable using "Inject Bamboo variables task" and "script task" to pass on variables to other tasks. This feature is documented here. Let me know if that helps. Cheers, Jey

Hey @Mike Newton , this appears to be an old thread. There are multiple issues discussed here. Which issue are you referring to? Which version of bamboo are you running? Cheers, Jey

Hi @Martin , I was going to suggest Bulk edit feature, but then I realised there is no option to add a job/stage/task to all of your existing plans. If you decide to manually introduce changes to all of your plans, I recommend you to create a new stage at the end of your plan and enable Final stage option (available since…

Hi @Carl Davis , The error message "Connection refused" usually means that the port that accepts database connection isn't open. Have you double checked if the port 1433 (from your JDBC string) is open between the application and database server? If bamboo is running on windows, you can use the following PowerShell command…

Hi @sshrivastava22 , It is possible to configure all these plans to run sequentially by configuring dependencies. You can make PlanA as a parent for PlanB, and so on. This way, once Plan A is done running, it triggers other plans sequentially. There is no option to disable a plan once it is finished running. Could you…