Comments
-
Hi @Luca Donnaloia yes you can use custom LLM also in the fix-flaky-test-custom-pipeline . You can use the supported LLM providers in the pipelines as described below """ my-agent: prompt: "Explain this repository" provider: codex """ Please check these blogs for more details on claude and codex support…
-
@amcroce Thanks for reaching out! The issue has been resolved, and branch deletion should be handled correctly going forward. Let us know if you run into any further trouble — happy to help!
-
Here's a reply you can use: Thank you @William William ! Really glad to hear you're excited about merge queues — that's exactly the problem we're solving: fewer broken builds, less rebase churn, and a smoother path to main for busy repos. We're looking forward to hearing about your experience once you've had a chance to…
-
Thanks @Carter Gray for the thoughtful feedback! Glad the PR-based workflow resonates — keeping a human in the loop was a deliberate design choice, not a constraint. We conciously didn't want it to start merging code without review. But would love to hear your thoughts. On the complex cases you mentioned — timing issues,…
-
Hi @Ren, thanks for raising this and for checking the docs! We haven't yet exposed the merge queue specific API but there are some fields in the existing PR apis which can help you identify the status of the PR. But to make sure we point you at the right thing (or capture a gap properly), could you share a bit more detail…
-
Hi everyone 👋 I’m jumping in with an update, since this thread has had a few folks asking for “native” merge queue support in Bitbucket Cloud. Back when this question was asked, the only options were custom Jenkins gating, REST scripts, or third‑party apps. Bitbucket Cloud now has built‑in merge queues, currently in open…
-
@Samuel Mezger Thanks for the feedback — really appreciate it! Some information to (even succeeded) tests can be written to stdout Quick question: we do show the full stacktrace for the failed tests in the pipelines tab and for the passed tests is there any other specific information from the xml file you'd find useful to…
-
Thank you @Adam Sajko and @Dimitar Nestorov for your comment and for taking the time to share how you're using Bitbucket Pipelines — that context really helps us. The request to automatically cancel an in‑progress pipeline when a newer one is triggered on the same branch/PR is definitely something we understand the…
-
Thank you @Chris Hatch - Eulo Labs for pointing the broken link! Let me get that fixed, in the meantime Here is the docs link which you can refer to
-
Sounds good @antti.peltola , thanks for being open to a call! You can book a time that works best for you next week using this link:Bitbucket Pipelines: Product Discussion - Rajkumar Singh Once you’ve picked a slot, I’ll confirm the meeting and share an agenda so we can make the most of the discussion. Looking forward to…
-
Thank you @antti.peltola the thoughtful feedback — this is super helpful. Quarantined tests / using data outside BitbucketWe’re planning to expose this data via APIs (and potentially other integration points) so customers can pull quarantined test information out of Bitbucket and use it in downstream systems or build…
-
Thanks @Jeff Cook for the thoughtful feedback — really glad to hear you’re looking forward to using the feature! On self-hosted runners: support isn’t available just yet, but it’s definitely on our roadmap. In the meantime, can I ask — are you using self-hosted runners across all your repos, or do you have any…
-
Thank you @Andrew Simpson for taking the time to write this up and for linking the code coverage request. We absolutely agree that code coverage visibility is a core part of testing, and that it pairs naturally with any work we do around test reliability. We don’t have anything concrete to share yet on coverage…
-
@Stijn Post thanks for the extra context and for sharing how you’re using testomat.io today – that’s really helpful. We’ve created a feature request to better support your use case: https://jira.atlassian.com/browse/BCLOUD-23991 We’ll use this ticket to gather additional interest from other customers with similar CI/CD…
-
@Paulo Henrique dos Santos Eiterer Thanks a lot for sharing this, and for already integrating with Bitbucket via the build status API – that’s super helpful context. Right now, posting JUnit-style XML reports directly via the Bitbucket API (without using Bitbucket Pipelines) isn’t supported. The current version of test…
-
Thanks so much for the detailed feedback, @Stijn Post @Ben Ford – this is really helpful context. You’re right that limiting this to the default branch isn’t ideal for many CI/CD setups, especially where you’re enforcing PR rules and doing most of your validation on branches like development before anything reaches…
-
@Yuxin Wang Yes the tests running in the child pipelines should show up in the Tests UI as long as the pipeline is fulfilling the criterrias mentioned in this thread
