Daniel Santos_157bm4 Atlassian Team

Hi @ryanbannon As you already know this is not an available feature. The only option I see for you regarding credentials is temporarily updating them in the Bitbucket Repository configuration >> Repository variables before running the manual build. I've opened an improvement request for this in order to track interest in…

Hi @Wellard These warning messages are not conclusive by themselves. We will need to check what error messages were logged before them to get better clues on what could be causing this scenario. I was able to find a similar case in our support channel and it was caused by a SQL Server not being able to accept connections…

Hi @Joseph Clements YAML specs was designed for less complex builds and therefore lacks in features if compared with JAVA Specs. Recently we had a lot of improvements in YAML specs due to a number of feature requests we received. At the moment you cannot have other repositories configured/linked to YAML specs. Of course,…

Wow! You have them both, skills and a beautiful office view!

Hi @Mahesh Pawar, The hardcoded number limit is the size of INT in JAVA which is 2,147,483, 647. We can't guarantee you will be able to reach this number considering other resources like DB size, disk space, artifacts storage etc. I was able to run a test with the queries from Solved: Can I edit the Bamboo build number and…

Hi @Bharath_Venkat_Rajan, I'm sorry, I didn't have time to answer your message. Yes, I would say that any time you need terminal you can use a script task for that. I'm glad you found your own way. =]

That is great @Ilan Hazan, thank you for taking the time to share your solution here =]

Hi @John Verburg According to the below stack trace line, I think there is a good chance that this problem is caused by a permission issue: at uk.org.simonsite.log4j.helpers.FileHelper.isReadable(FileHelper.java:115) I would suggest investigating two possible causes: * Make sure all the files in both <Bamboo_Home> and…

Hi @Andrew Lehman, Yes, I can confirm there is no dashboard for this in Bitbucket pipelines at the moment. We do have a feature request for it open: * #12765 - Pipeline wallboards — Bitbucket I can't tell you this will be available soon, but I'm sure that having more votes in the above feature request will accelerate the…

Hi @phlo_z, entityID The entityID is the ID used to identify the project/plan/job in the Bamboo database. That is a design issue that blocks this API to be used only through a sequence of rest APIs. There are some improvement requests related to this issue already reported: * [BAM-19660] REST APIs for Projects should show…

Hi @Hamed Beiranvand, To allow an anonymous user to trigger change detection you need to enable the following security option: * Admin >> Security settings >> [ ]Allow anonymous users to trigger remote repository change detection and Bamboo Specs detection Your instance should be able to get the branch deletion even if…

Hi @Mahesh Pawar I'm curious about what specific log count you are referring to. * Are you talking about build results? * Or are you referring to other server logs? If you clarify that I can probably investigate that for you.

For sure @Matthew Lieder! Thank you very much for sharing your issue, logs and following up with the solution. Have a good one!

Hello @christok Please tell me that you can use a bash script for that! Otherwise, you will need to transcript the script I just did for you. It uses the following rest APIs: * /rest/api/latest/project Get the list of projects * /rest/api/latest/project/$PROJECT?expand=plans Get the plans from a given project *…

Hi @Matthew Lieder I've seen a similar issue and it was caused by the Git version installed in the Bamboo server. * Do you mind checking the Git version and sharing it with us? Even better if you can update it and check if this problem will still persist it would be great. * Have you tried to delete the repository case…

Hi @[deleted], Pipelines consider bitbucket-pipelines.yml file in a given branch to trigger the build and run the specified tasks. Examples of situations that may happen: * A commit arrives in develop. The bitbucket-pipelines.yml from branch develop will be checked and if it has rules to run a build on develop the build…

Hi @Raiyan Ishmam, As far as I know, the sections represented by anchors cannot be merged. They can be updated with <<: but not merged. It means that you can only reference one script section per step, not two of them in the same step/script. You don't see any YML validation error due to the problem reported here: * Better…

Hi @Manoj Kumar Thank you for sharing the build logs, they are very helpful. I want to highlight these lines: error 24-Jul-2019 14:54:59 Caused by: java.io.IOException: There is not enough space on the diskerror 24-Jul-2019 14:54:59 at java.io.FileOutputStream.writeBytes(Native Method) It seems that the checkout is failing…

Hi @[deleted] The test tab will only show the test results that failed and the error message will depend on the XML report produced. Bitbucket pipelines will be compatible with xUnit/JUnit reports. You can get more details here: * Test reporting in Pipelines - Atlassian Documentation I would suggest you check the report…

Hey @daneshrao, Bamboo does not have a migration feature like Bitbucket to perform such change. To migrate the DB in Bamboo you will need to export the database and import it in a clean installation with the selected DB. The process is described in this document: * Moving your Bamboo data to a different database -…

Hi @Vineesh, That type of error can have two main causes: * The file is not there. * The file somehow has restricted permissions. How to mitigate them? * Check if the file is there or add an extra command in your build just to check that. You can navigate to that directory in the terminal after the build as well. Make sure…

Hi @Amir I'm glad it worked and you now have your remote agent available! Have a great day! 

Hi @[deleted], Thank you for all the details you shared about this. They help us to better understand the issue you are facing there. From what I can get, It looks like your LDAP is restricting its responses to 500 users max. Bamboo and Bitbucket are configured by default to request all users at once and usually, LDAP…

Hi @daneshrao We have a document that describes the process of migrating your data from one database to another which is described in this page Moving your Bamboo data to a different database. If you found this document and struggled in one of its steps, can you described where exactly you are facing issues? That would…

Hi @Lahiru Malepathirana Thank you for bringing your question to Atlassian. You are more likely to get an answer to this question in a different community. I encourage you to create another post at https://community.developer.atlassian.com. Let me know if you face any issues to submit a post there.

Hi @Tem Ed, I'm glad it worked! I hope now things go smoothly =] Have a good one!

Hi @Ilan Hazan I don't see a better option to get the information you want other than using REST API and asynchronously checking if the build finished. I have a suggestion for small improvements in your approach. * Try to use jq (JSON processor) to filter the request responses. There is one example you can see jq being…

Hi @Jens Mühlenhoff Thank you for the feedback. Do you mind sharing your ideas on how this document could be improved? I recently created a couple of requests to improve this doc, but I'm pretty sure there is more to be done. Thank you!

Hi @Arjun Gandhi, Yes, you are correct. Configuring the repository this way you will not be using Bitbucket Cloud APIs, just normal git API. Due to this detecting commits and branches will occur through polling (which is configured by default to 180s for commits and 300s for branch detection.

Hi @Kevin Matlock Thank you for the feedback. I've opened the following feature request to address this issue. Voting on it is a good way to flag this as something important. * [BAM-20537] Lack documentation on Java repository stored specs permission to access other repos Have a good one!