Edmund Munday Atlassian Team

Comments

  • Hi everyone, we've finalised our plans for the implementation of a premium runners tier and have published all the details via a dedicated Bitbucket Cloud blog post. There are important details contained in the update that relate to the migration from the existing runners implementation to the new free/premium tiered…
  • @Alex Fok & @Stanislau Yarotski - We're working on implementing artifact sharing between parent/child pipelines currently. Hoping to have it available in early April. The objective with this is to be able to effectively treat child pipelines like "function calls", allowing you to pass variables and artifacts from the…
  • @Asher Pix & @Asher Pix - we're investigating this now, apologies for the delay.
  • Hey @Dani Asztalos - thanks for catching this, I'll update that now. I'd say this will teach me not to blindly copy/paste code from engineers... but we all know that would be a lie.
  • Hi all - we're needing to cancel the session for the 26th of September sorry due to public holidays in Australia. Apologies for the inconvenience.
  • @Mike Turalenka - that's a really excellent point, thanks for raising this. We're going to have a look into something along the lines of what you suggested. Can't promise anything right now, but you raise a really good point, so hopefully there's something nice and simple we can do to prevent clogging up your UI.
  • @matteo_castellotti - that is the expected behaviour for the moment, child pipelines are currently quite encapsulated and do not share much context from the parent. More advanced context sharing is the first thing we're working on post-release. Just for our reference, would you be able to share an example of the use-case…
  • @Ori Saporta - great questions: As of today, child pipeline are entirely encapsulated and can't consume context from the parent, just the repository and workspace. However, context sharing from parent to child is literally feature #1 on our "coming next" list and we will be making that available soon. This will work very…
  • Update: We've identified the issue causing this behaviour and will have a fix deployed by EOD tomorrow. Depending on your geo, I'd suggest giving your workflow another try on Friday. Thanks again @Chris Callahan
  • @Chris Callahan - thanks for your feedback, checking this with the team now - we'll have an update for you in the next 24hrs.
  • Hi everyone - I'm extremely sorry, due to a family emergency I've had to step away and won't be able to run the office-hrs call tonight. I'm VERY sorry to everyone for the inconvenience, but this was something quite urgent.
  • @Andrew McMorris - the first EU session is 25th of April, by which point it SHOULD be 8am rather than 7. I know that's still very early! @Aditya Singh - Pls download the calendar invite from the link above so that the meeting sessions can be converted to your local timezone. @Stefan Schindler - The Slido link should be…
  • Hey @Pascal GUINET - I'm guessing your comment is in relation to the time slot? We've updated the timing to an alternating months model, one month with a NA/APAC friendly time slot, the other with an Asia/EU friendly time slot. Please make sure you're using the most up to date version of the invite from the link provided.
  • Thanks @PierrickPuimeanChieze & @Jason Harrison - if the concern is regarding secrets that are defined within the pipeline execution (aka - never interacting with the native Pipelines Secured Variables feature), then this is a scenario we would say we are explicitly not trying to support. Variable sharing is for sharing of…
  • Hey @Michal Šimon - that's really interesting you mention that, this is a concept we've been playing with in a different way via a concept we're calling "remote steps". Effectively a remote step would work by defining a URL that we would effectively fire a webhook event at, with the payload including all the context about…
  • Hey @Jason Harrison - so I think I understand your question now, sorry. Just to confirm, the risk you're raising is someone using this feature to effectively "proxy" (for lack of a better term) the value of a secret out of the build context it's made available in via an exported variable? So for example: // Existing secret…
  • Hi @Jason Harrison - to be VERY clear, this feature is NOT designed to be a secure/encrypted mechanism to pass secrets between steps. We strongly recommend utilising a dedicated 3rd party secret management tool via our generic 3rd Party Secret provider interface. Hypothetically, if you wanted to pass things like…
  • Hi @Kirsty Mullen - apologies for the delayed response to your message. We've identified a performance regression specifically in some node environments that do very high volumes of read/write operations to disk. We have identified a fix for this issue and are in the process of implementing that now.
  • Hi @jacky Solanki - thanks for the feedback. The issue you're seeing is due to the usage of a "script" block within the Jenkins pipeline. Script blocks rely on Jenkins implementation of a native Groovy runtime and break outside of the declarative pipeline framework. As we mentioned in the release blog for this…
  • Hi @Jeffrey Hsiung - you can manage multiple users who have contributor access to a single Forge app via the Forge Developer Console: https://developer.atlassian.com/platform/forge/manage-app-contributors/ Different users can be given different levels of permissions depending on what you want them to be able to do. Each…
  • If anyone else is seeing measurable performance degradations of this kind of scale, please reach out to the Bitbucket Support team so that the engineering team can troubleshoot the underlying cause. We do expect some customer to see a change in build speeds, but not an overall degradation. The reason for this is we have…
  • Hi all. * A few people have raised concerns regarding how these changes were communicated which we wanted to clear up here. * These changes were communicated with six months, 3 months, and 2 weeks notice to all customers of Bitbucket Cloud via a range of different comms channels. * These comms channels include:* Multiple…
  • Hi @Michael Klassen - I'm the Product Manager for Bitbucket Pipelines. Wanted to quickly reach out re: your comments around the increased cost for static IP's. If you haven't already seen it, I posted this update a few months ago going into the details of exactly why this change was necessary in order to be able to…
  • Hi @Aurimas N_ - thanks for the question, you raise a bunch of really excellent points. To put it plainly, we're very aware of the gaps that exist right now in terms of Pipeline composability and reusability, and it's going to be one of the top focus-areas for us over the next 12 months. --- > Most of the questions…
  • Hi @Garrett_LoVerde So the use-case you're talking about here should be absolutely achievable, we've discussed similar use-cases with other users in the past. You might need to reverse the order of operations/thinking a little bit though. e.g You'll probably need to have a dedicated batch of runners for each of the…
  • Hi @Georg Duemlein - great question! The Code Search API is definitely the way to go for that. You can make a search in a particular repo (or across multiple repos) using a Glob style search syntax and look for your `iac` directory when your Dynamic Pipeline runs. Another option if you want to implement logic only when…
  • Hi all - please see: https://community.atlassian.com/t5/Bitbucket-questions/Re-Why-do-I-see-the-completed-pipeline-status-as-quot-Paused/qaq-p/2710948/comment-id/104654#M104654
  • Hi all - apologies for the confusion around this change. There are several small incremental changes currently underway designed to give users more a more explicit set of statuses for builds - in addition to giving users more tools to better manage those statuses - what you are seeing right now is one step, of several,…
  • Hi all - just a quick note to let everyone know that we've now added support for Deployment, Environment, Environment Variable, and Repo variable API's for Forge apps. Details are here: https://community.atlassian.com/t5/Forge-for-Bitbucket-Cloud/Additional-support-for-Pipelines-API-s-from-Forge-Apps-for/ba-p/2696769