Justin Thomas Atlassian Team

@Jonathan Gjertsen Currently Bitbucket doesn't expose labels any Runner related details to the steps. I do understand the use case and the feature request is on our backlog. We are currently working on other high-priority features such as Windows and MacOS support for Runners. 

@ntmat Caches work the same way for both cloud and self-hosted runners. Be aware that the performance improvement from caches is different between cloud and self-hosted runners. Self-hosted runners are located in your data center, so it might take more time to pull the cache from Bitbucket. 

@polRk There are multiple things that can impact the speed of a step on a self-hosted runner. Network latency is a known cause to slow down builds in self-hosted runners. I would suggest getting help from Atlassian support to debug the issue. Thanks for trying the runner.

@Luis Plaza Thanks for trying out the runner. As self-hosted runners is in beta the REST APIs are still internal, we will be making it public when we go GA. I would suggest not depending on the internal APIs till then. Thanks

@inger_klekacz The entry represents the source branch. As per your example, it would be `branch`. I will raise an internal ticket to update the docs, thanks for the feedback.

@Brad Vrabete You can currently start a runner in a Kubernetes cluster, auto-scaling is not yet supported. Here is an example of Kubernetes spec for a self-hosted runner. Please let me know your feedback. apiVersion: v1 kind: List items: - apiVersion: v1 kind: Secret metadata: name: runner-oauth-credentials # labels: #…

@san As part of removing the limits on runners, we will be also looking at removing the max-time limit.

@mohit_saw You would have to manually clone project B in project A's pipeline and then build it. Steps to clone another repository can be found here. Hope this helps.

@Paul Fox Allowing shell access to the host machine is on our long-term roadmap, we will start exploring it after Windows Runners. Thanks for your feedback.

@Martin Cassidy Please use the community to provide your feedback, but if you run into any bug or have issues using the runner please raise a support ticket.

@Colin Panisset (Cevo) Yes, workspace runners will allow you to use a single runner between multiple repositories, we will also soon remove the limitation of one runner per machine.

@Rochak Saini As part of removing the limits from self-hosted runners we will be exploring the option to allow access to GPUs. Thanks for your feedback.

@Fabregas4 Please have a look at this answer.

@Fernando Arteaga We don't currently support overriding variables. Have you considered using deployment environments to override variables?

@emanuel Have you considered using Bitbucket Pipelines Runners for executing your pipeline? Bitbucket Pipelines Runners allows you to execute a pipeline on your own infrastructure. 

@Deepu Chandran This shouldn't be happening, can you please raise a support ticket?

@alstaroverov The Bitbucket Pipelines definition is based on the branch that has changed. For example: If I push a commit to the development branch, then bitbucket-pipelines.yml from the development branch is used as the Bitbucket Pipelines definition. Please let me know if you have further questions.

@Bryson Sullivan You can use Bitbucket Pipelines Runners to deploy to your local website. Documentation can be found here.

@AbhishekRsv You can use the following REST command to create a deployment environment. The endpoint is not yet documented, I have raised a ticket to add it to the public documentation. curl 'https://api.bitbucket.org/2.0/repositories/<workspace>/<reposlug>/environments/' \ -u <username>:<password> -H 'content-type:…

@Ingmar Yes, a runner can execute only one step at a given time. We currently have a restriction where you cannot start multiple runners on a single machine, we will be adding support for that in July. Thanks for trying the runner.

@Manuel Serret Thanks for trying the runner. The issue with minutes being consumed with self-hosted runners has been fixed, please raise a support ticket so the minutes can be added back to your account. We are still working on adding the SSH Keys feature to runners, it should be available in a couple of weeks.

@[deleted] I believe wpengine is blocking the `git push`, can you get in touch with their support?

@Daniel Mackay The current runners doesn't support windows. We will soon be working on windows runners and as per the current plan, it will be available in Q3 CY21.

@Colin Panisset (Cevo) Runners is now available to everyone, the announcement has been delayed because there are a couple of bugs that we like to fix before it's broadly used. Please try the runner and let us know the feedback.

@Srikanth Mamidala Have you explored trying conditional steps?

@Ming Han Chung Yes, the service container name is defined as part of the definition. Can you share your pipeline's yml?

@Jason Ausmus Bitbucket Pipelines doesn't support using variables as key for deployment, you will have to statically define the deployment environment. - step: &terraform_update image: name: <image> name: Update Terraform deployment: prod-deploy script: - do stuff

@Hardik Have you explored creating the .env file in your `step` from environment variables that you can define at a repository level?

@marcelo_quintas You can use self-hosted runners to access your private network. The self-hosted runner is in EAP and soon it will be available to everyone. 

@[deleted] By default, Bitbucket Pipelines does a shallow clone and you need a full clone if you want to push to a new remote repository. You can do a full clone by enabling it at a step level - step: name: Full clone clone: depth: full