lassian Atlassian Team

Hi @Peng Xi We do not support arm yet, please upvote this issue https://jira.atlassian.com/browse/BCLOUD-21412 @Justin Thomas do we have a rought estimate when we are looking to add Arm support? Kind Regards, Nathan Burrell

Hi Mischa, Yep if you use runs_on we would ignore that setting, as we dont fail parsing on unknown properties as some users have added extra properties to the yml, and it would fallback to using a cloud runner which we do bill for. Kind Regards, Nathan Burrell

Hi, Ahh yep your on the free tier of usage, I dont believe that can raise support cases. Can you please provide us than the output of `docker system info` and also your complete runner log file which is located under your runners working directory (by default /tmp) its called runner.log. That way we can better investigate…

Hi, Can you please a raise a support case at https://support.atlassian.com/bitbucket-cloud/ That way we can investigate with you the error better. Kind Regards, Nathan Burrell

Hi @alexey So thats by design as no runs-on is backwards compatible with all existing steps which means to use our cloud as you can mix and match cloud runners and self hosted runners within a pipeline based on lack of no runs-on as you can share caches, artifacts etc between them. I can see your use case but you would…

Hi @alexey Can you describe what you mean by default runner? You mean a fallback if none are found? If so that can be problematic as labels are used to match a runner that can run that step, if it falls back to some default it may not be able to run the step as the default runner may not have the capabilities that the…

Hi @itsmesunil We are currently working on the ability to allow users to add runners at the workspace level to be shared amongst the repositories in the workspace. Keep an eye out for this feature in the coming weeks :) Kind Regards, Nathan

Hi @Sander Mol Correct we dont and wont charge for minutes consumed by steps running on runner regardless of what limits/run-time you use. Kind Regards, Nathan Burrell

Hi @plussier Your yml file is incorrect you need to use `runs-on` not `runs_on` as we ignore unknown properties its thus not reading your runs_on and scheduling on our cloud runner which is the default behaviour when a step doesnt contain `runs-on`. Kind Regards, Nathan

Hi @Erwan d_Orgeville We dont support windows containers, we do support linux containers on windows using docker for windows. Can you please raise a support case, so we can investigate this. Kind Regards, Nathan

Hi @Riccardo Trivellato Can you please raise a support case so we can investigate this issue. Kind Regards, Nathan Burrell

Hi @polRk What do you mean macos runner? We dont currently support macos are you meaning running it under docker for mac? The first time you run a step it will have to pull the images from the docker registries which may not be geo located close to you, same for artifacts and caches. In the cloud we have a registry mirror…

Hi Trydalch, Can you raise a support case so that we can re-allocate your minutes. Will your fix allow pipelines to be run on self-hosted runners when all build minutes have been consumed? The fix is going out that will allow for this aswell. Kind Regards, Nathan Burrell

Hi Trydalch I have just identified an issue with the logic, if you could raise a support case we will return the minutes to your account. I am deploying a fix to ensure these wont be counted for future steps. Kind Regards, Nathan Burrell

Hi Trydalch, Any step that uses runs-on does not currently count against your monthly quota as they are running on your hardware. Can you please provide us your workspace uuid and repository uuid so we can investigate this. Kind Regards, Nathan Burrell

I also created a ticket internally to return a response header indicating if we proxied (augmented the request with authorization headers) or not so in the future itll be easier to debug.

Hello, From looking at your request it appears your using the auth proxy but your using https rather than http. We forward the request authenticated to bitbucket over https but we require you to use http to talk to the proxy running alongside your step.…

I have created a feature request for this in bitbucket, please add your comments to it regarding adding support for this. https://bitbucket.org/site/master/issues/17946/allow-users-to-configure-insecure-docker

Hi Benjamin, It appears from reading the github issue that the pytest-redis library starts redis itself, which means there is no need to use service containers (as they would start redis in another container again). You would need to either wait until that library is updated such that it can be configured to connect to an…

Hi Nicolas, In the first yaml example you provided. pipelines: default: # This step installs dependencies that should be cached its however not configured # with a pip cache so it is not generating one. - step: name: Lint by Flake8 image: python:3.6 script: - pip install flake8-bugbear flake8 - flake8 bvp # This step…

Hi Enduser6, Pipelines does not have a feature currently that can based on the contents of a commit change how the step is executed, you would have to instrument a step to perform this logic for you (maybe by having as the first step in a pipeline some code that does this filtering and makes the calls out to jenkins based…

Hi Trurl, We dont currently publish a schema for our yaml format :( The closest we have is you could create one based on the description of our yaml as described here: https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html Kind Regards, Nathan Burrell

Hi Warren, Can you please either provide us the yaml for the pipeline that is exhibiting this behaviour or raise a support case via https://support.atlassian.com/contact (so we can investigate further, as from the screenshot I cant see the image or other context about the container you are using :)). Kind Regards, Nathan…

Hi Sebastian, Is this still occuring? If so can you please raise a support case via https://support.atlassian.com/contact (so that we can investigate further). Kind Regards, Nathan

Hi Nicolas, Are you expecting the pip cache to be cretaed by the first step and consumed by the second? From looking at your script commands it appears that way (as the first step installs some pip dependencies that you want cached and the second runs tests that i assume use said dependencies). If so you need to add the…

Hi Aruljothi, From the error above its saying that pipelines cannot pull the javascript dependency igtb-digital/intellect-authentication-services-module. Is this a private dependency, if so have you setup your npm credentials in your step correctly to pull that dependency. Kind Regards, Nathan Burrell

Hi Carlos, Can you either provide us a link to the pipeline that this is occuring for or alternatively raise a support case so we can investigate this further via https://support.atlassian.com/contact Kind Regards, Nathan

Hi Muhammed, It appears that in each step you are setting up parts of the environment in order to run your python tests. State however in pipelines does not carry along automatically, each step is a fresh container, you can pass along artifacts between steps but tht would not help in your yaml above. First can you change…

Hi Albert, Could you provide an example of your yaml configuration. If the second step, that deploys to production, is it a manual step? If so there is currently no feature in pipelines to automatically kick off this manual step triggered conditionally based on the contents of a commit. Kind Regards, Nathan

Hi, Is it possible to provide a copy of your dockerfile for reference so we can see how the layers are being generated, or alternatively a link to the build (raised via a support case). Kind Regards, Nathan