Justin Thomas Atlassian Team

@t1279k Can you please contact Atlassian Support to debug this further?

@a.farouk Bitbucket Pipelines allows you to trigger only one build for any tag/branch/ref changes. If you want to run a common step across multiple pipelines I would suggest using YAML anchors. YAML anchor should allow you to reuse step defined in the default pipeline across tag api-1 and api-2.

@Kevin Alejandro Hernández Rodríguez Are you caching the node dependencies and can you try after disabling the cache?

@Thirukumaran Kubendran Can you please explain a bit more about your use case?

@Mikhail Sapozhnikov Bitbucket Pipelines currently doesn't have a way to specify a before script, you will have to add it as the first line for each of your steps. There is a feature request to add before script support, please vote for the issue.

Have you considered splitting the tests into groups and then execute them in parallel using the parallel steps?

@Alan Andres Haro Can you please explain a bit more about your use case? We are currently working on Bitbucket Pipelines Runners, please join the EAP if you would like to try it out. 

@Monica Gordillo Currently Bitbucket Pipelines doesn't have the capability to request approvals for deployments within the product. Bitbucket Pipelines does have integration with Jira Service Management which allows you to request…

@duy.huynh This shouldn't be happening, can you please raise a support ticket so we can investigate this further?

@Sasank Sarma Have you tried to set an alternate path for the settings? mvn clean install --settings <repo-path>/settings.xml

@Eytan Yammer Currently Bitbucket Pipelines doesn't support dynamic parallel steps. Are the max containers a constant? If that is the case, I would suggest having a step for all the containers and skipping them if it's not required to build the container based on the artifact. 

@Akshay b You can use a self-hosted runner to do a deployment to an on-prem cluster. The Bitbucket Runners is currently in early access, we are planning to make do an open beta in a couple of weeks. Please join the early access program to get access to Bitbucket Pipelines runners.

I might be missing something but If you start docksal/web as a service it will not have access to your source code because the source code volume is not mounted to the service.

Is `docksal/web` started as a service or do you use docksal/web as the base image for the step? 

@Azamat Kalmurzayev Yes, we are planning to have a non-container version of the docker which would allow you to execute commands on the host machine. Unfortunately, I cannot give you a timeframe of when it would be available because we are still in the feedback gathering phase. We will be prioritizing the feedback soon…

@Andy Gikling Can you please create a question in the EAP community group with the logs, so that we can debug the issue and fix it? The runner should have worked or at least logged the error. Thanks for trying out the runner and reporting the issue.

@Mike Prince I am not an expert in python development, but I don't think we need to worry about Issue #1 since the environment will be created if it doesn't exist. Issue #2 is a bit tricky since we need to invalidate the cache when environment.yml is updated. You can use the cache clear pipe to achieve it. image:…

@bsuttis You should be able to access your webserver at 127.0.0.1. Are you starting the webserver in the step or as a service?

@Fayas Mansoor Thanks for the interest, we will be expanding the cohort as we add more features to the runners and bring it to feature parity with the cloud runners. We hope to allow everyone to try the runner by the end of April.

@drlundgren We will need to test it, but we hope the non-container version of runner would run on FreeBSD. Thanks for your feedback.

@Martin Rakovec We do plan to build a runner which would give you direct access to the shell on the host machine. Hope that would enable you to perform tests against real hardware. Thanks for your feedback.

@t1279k Have you explored the option to use parallel steps with a manual trigger?

It looks like the git lfs clone has been deprecated and git clone has similar performance. 

Hi @t1279k It looks like the blog is a bit dated. We have added the capability for user-defined deployment environments, you need to now define your environment before using it in your bitbucket-pipelines.yml. Further documentation can be found here. Thanks, Justin Thomas Product Manager, Bitbucket Pipelines

I have lots of object to be worked on, so git clone step should be LFS enabled. @oguzhan Can you explain a bit more about what do mean by objects? Is it the large files tracked by git lfs? Have you tried using git lfs clone command to speed up the clone?

@Uri Simchoni The self-hosted runner is currently packaged as a container and similar to Bitbucket Pipelines architecture, each step is executed in a separate container. The initial release will have restrictions around the resources, but in future, we plan to remove those restrictions. Hope this answers your question.

@Lewis Chung In the initial release the self-hosted runner will have the same resource limitation as the cloud runner. In the future, we will be relaxing the limit and allow you full control of the hardware and resources. Thanks for the feedback.

@tperlaky Steps running on the self-hosted runner will not consume any build minutes.

@Albert Palomer We will be adding Windows support to Runners, it's on our roadmap. The current plan is to start work on it after Runners GA.

@crypton1 To ensure we can respond to every feedback, we are controlling the group size and expanding it slowly. I have send out another batch of invite and I hope you have got the invite.