Justin Thomas Atlassian Team

Thanks @Yatish Madhav Keen to hear your feedback!

@Greg Draper We also have a lot of cases where someone is a Jira space admin for more than one space and they want the spaces to share schemes and other settings, but they want to maintain control. Can you please elaborate on the type of control?

@Joao Zampa I understand the reluctance to retry TMPs after that experience. The Space policies open beta addresses part of this: admins can require reuse of global fields and statuses while teams manage their spaces within those boundaries. This also solves the cross-space reporting problem because now all spaces used the…

@Andree Lindenblatt Thanks for the feedback. We recently shipped Replace Status in the workflow editor, which lets you replace an existing status with a Global Status.

@Josh We have recently launched an Open Beta for Jira: Space Policies that allow to enable governance on team-managed spaces across Jira, JSM and JPD. Please give it a try and let me know the feedback.

@Cornelia Jeppsson Can you please raise a support ticket to debug this further?

@Yaron Norani It's currently not on the short-term roadmap. Please follow the feature request to get update on it

@Adrián Plaza Unfortunately, permissions for Components are not currently on the short-term roadmap. Please vote on the feature request and watch it to receive updates when we pick it up.

@Jacques The feature has been rolled out to all customers on the continuous release track. Is your site, by any chance, on the bundled release track?

Hi @Mark Haller, This is Justin Thomas from the Jira team. Thank you for your feedback on Guest users in Jira. To set the right expectations, we will not be addressing this feature in the near term. You can check our new feature policy for more information on how we decide what we implement. Please vote and watch…

Kubernetes is the first platform that we decided to support in the autoscaling tool because Linux runners are containerized, K8s is quite popular, and easy to deploy containers on it. If we see more requests for the AWS EC2 platform we will add support for it. I am not sure about the effort required to add EC2 support.…

@Nicolas Esteves Yes, the current tooling only supports Kubernetes. Can you please explain your use case and your plans related to runners?

@Nicolas Esteves Apologies for the wrong link, please try this one. I have updated the initial comment with the link.

Hi @Nicolas Esteves , I am excited to announce EAP for Runners auto-scaling tooling. If you are interested in giving it a try, please join this community group. Thanks, Justin Thomas

@Michal Czeraszkiewicz It's great to hear it worked. Yes, we will be adding these steps to the documentation.

Hi @Michal Czeraszkiewicz , Following is an example to integrate with GCP using OpenID Connect. Please let me know if you have any further questions. Step 1: Creating a Workload Identity Pool In this step, you are going to create a workload identity pool which is a container for a collection of external identities. gcloud…

@Mathieu Lemay Yes, we will be supporting it on cloud runners. We are currently currently blocked by a bug in BuildKit. We will be enabling BuildKit on cloud runner once the bug is fixed or when we find a workaround.

@Marcos De Melo Da Silva Yes, auto-scaling is on the roadmap. We are aiming to release it in Q2 of CY2022. We will most probably be doing an early release next month, if you are interested please follow this ticket.

@[deleted] The team will work on macOS runners after shipping Windows Runners. macOS runners are non-containerized and it should be possible to use them on a Linux machine. The current plan is to ship macOS runners in the first quarter of CY22. You can follow this ticket to follow the update.

@Pratap Mundasada We are currently working on Windows Runners and aiming for an EAP in November. We will soon update you on an exact date.

@Monica Gordillo Currently building multi-arch images is only supported using a self-hosted runner. An example can be found here

@Mohammadreza Koohkan Bitbucket Pipelines Runners is in GA, you can start using it today.

@Bharadwaj Sattaru Can you please get in touch with Atlassian Support, they will be able to help you.

@chris_ng You should be able to execute it on K8s. Please get in touch with Atlassian support if you run into any issues.

Hi @Sathish Puranika Kadinakonda I would suggest contacting Atlassian support, they can help you with the error. Thanks, Justin Thomas

Hi @AbdAlrahman AlaaEldeen Bitbucket Pipeline Runners are now in GA. You can now run multiple runners on the same machine. As for the short-term roadmap, we are currently working on Windows Runners and then we will start work on non-docker/macOS runners. Please let me know if you have any further questions. Thanks, Justin

@Oliver Werner We will not be charging Bitbucket Pipelines Runners on usage, there won't be any additional cost to use Runners.

@Joris Vleminckx Can you please get in touch with Atlassian support, they may be able to help you.

@lucas.ferreira Bitbucket Pipelines currently doesn't support OpenID Connect with Google container registry, it's only supported with AWS. Currently, you can only use OpenID Connect token to integrate with GCP from within the step.

Unfortunately, there is no easy way around it. Using a docker:dind service is a workaround and can help, but I think in long term it might complicate the setup. It depends on the performance impact. Cheers, Justin