Peter Plewa Atlassian Team

Hi @Alexandre LOUBEYRES At the moment the only way to do it is to use internal API that is hosted at: https://api.bitbucket.org/internal/repositories/{repository_path}/jira-issues This is not documented and prone to changes so I would not recommend doing so, I would suggest raising a feature request for either documenting…

Hi @karthik nayak What is the error you're getting? Thanks, Peter

Hi @Matthew Allen Your project may require adding `npm install`. Let me know if that helps. Thanks, Peter

Hi @Prakash Chettri Are you using AWS CLI or a pipe https://bitbucket.org/atlassian/aws-code-deploy/src/master/? Both should return logs that indicate state of deployment, additionally you can turn on debug mode for additional info. Thanks, Peter

Hi @Asad You may want to check out Elastic Beanstalk pipe at https://bitbucket.org/atlassian/aws-elasticbeanstalk-deploy/src/master/ and more information about pipes - https://confluence.atlassian.com/bitbucket/pipes-978200560.html and let us know if it solves your use case. If you require additional support please share…

Hi @MichaelHobo It looks like you'd want to trigger multiple pipelines for a push, that is currently not supported even though you could hack your yml in a such a way that the same branch would match multiple times like `master` `maste*` `mast*` etc. I would suggest raising a feature request describing your use case…

Hi @RH Becker Unfortunately it is not possible at the moment. There is a support request that you can vote on and follow https://jira.atlassian.com/browse/BCLOUD-13014 to get updates on this issue. Thanks, Peter

Hi @Pierangelo Repetti Sadly it is not yet possible. You could assign admin rights for particular repositories but that's probably not what you are after. It is definitely a valid use case and I found similar feature request at https://jira.atlassian.com/browse/BCLOUD-18024 if this is what you mean i'd suggest describing…

Hi @Virginia Elizabeth Gil Vásquez I've tried running few example projects from https://github.com/nestjs/nest/tree/master/sample in Pipelines and they all work just fine. This makes me think that it may be some specific configuration related to your project that requires checking out. Firstly Pipelines runs inside Docker…

Hi @pmosch There are couple of things that you're asking here, let me try to narrow it down: * Each pipeline step starts and stops Docker container and this prevents any process that you want to run to be shared between steps. * If you can start and stop the same process in both steps and both to share the same generated…

Hi @javi_micocar, Would setting clone depth as defined in https://community.atlassian.com/t5/Bitbucket-questions/clone-depth-does-what-Why-do-I-care-about-this-setting/qaq-p/496247 help out with your issue? Thanks, Peter

Hi @Rudolf Rödl I have my colleague answer: You can call docker stop if running it via docker run. We do call docker rm -f when you force stop through UI as we want to stop it as quickly as possible. Thanks, Peter

Hi @piyush05, Our Pipes integrations with AWS should be able to help you out here, have a look at https://bitbucket.org/product/features/pipelines/integrations and see the documentation. Alternatively there are few references that might be helpful…

Hi @[deleted], I would need more information to help you out here. Could you share your bitbucket-pipelines.yml file to help out with debugging? Pipelines simply runs your script from that yml file in a Docker container, can you try to run the same script in Docker in your local environment? Thanks, Peter

Hi @Tomas Svitil, This issue likely corresponds with an incident that happened recently, if the issue persist I would suggest contacting our support at https://support.atlassian.com/contact/. If it works fine and re-occurs in the future keep an aye on the Bitbucket status page at https://bitbucket.status.atlassian.com/…

Hi @ve, Firstly I would suggest following community thread at https://community.atlassian.com/t5/Bitbucket-questions/How-can-I-use-SSH-in-Bitbucket-Pipelines/qaq-p/347345 and our documentation https://confluence.atlassian.com/bitbucket/use-ssh-keys-in-bitbucket-pipelines-847452940.html both explain how to use SSH keys in…

Hi @Rafael Chebel, unfortunately we don't have estimates for this.

409 can happen if you are trying to submit the same variable name to the same environment, which needs to be unique.

Hi @itsjamesd, A step in Pipelines has 4GB of available memory by default. You can increase this to 8GB by running 2x builds: https://blog.bitbucket.org/2018/02/20/support-large-builds-bitbucket-pipelines/ When you add a service to a step it will consume 1GB by default. For example a step with a single service leaves 3GB…

Hi @Rafael Chebel, This is currently using undocumented internal API, feel free to use it but be aware that it ma change. Thanks, Peter

Hi @bridge This is currently not possible, I would suggest creating a feature request for it at https://jira.atlassian.com/projects/BCLOUD/issues/ Thanks, Peter

Hi @Habib Haider, This is currently not possible, we are aware of this and are gathering feedback for adding additional variable levels (project, team) at https://jira.atlassian.com/browse/BCLOUD-14959 I would suggest adding your feedback and watching above issue. Thanks, Peter

Hi @Marcelo_Anabuki, You can add Deployment Variables through API as follows with an OAuth2 access token. curl -X POST \ -H "Content-Type: application/json" \ -H "Authorization: Bearer {access_token}" \ -d '{"key": "key", "value": "value", "secured": false }' \…

It looks like the /dist directory is not being generated at all. It looks specific to your project configuration and there are number reasons this may happen. Does it work when you run the same set of commands in your local environment and when you try to run it in Docker?

Hi @Appan Ponnappan You are correct, the link in **next** section is incorrect and points to the wrong resource. I will mark it as a bug and get the team to triage, thanks for bringing it to our attention. In the meantime you should be able to construct next page url that is similar to the one you are using to fetch the…

Hi @Phil Fitzgerald I'd make sure that the image you're using has node installed, if that doesn't help I would need some additional information to help debug your issue. Could you share your YML and raw Pipeline Log? Thanks, Peter

Hi @Oleksandr Zaitsev Sorry for delayed response, did you manage to resolve your issue or could you provide me information with the current state of your pipeline? There are number of articles on how to connect to mysql service, is any of those helpful?…

Hi @Alexandr Marchenko You can definitely run a pipeline for pull request. Those get triggered automatically on any existing Pull Request updates, but if you rerun any of existing one you can see what the expected parameters are. It doesn't seem to be documented so you'd have to try few combinations to find required…

Hi @Mykola Fenyk Could you upload logs from the pipeline to help with debugging it? The error is not pipeline specific and I would make sure first that you can run above steps with the same docker image in your local environment. This is a reference that I found that may be…

Hi @Rob Wilson Could you upload full logs for both your mongo service and script? If mongo successfully starts all the time it looks like a race condition that you may be able to workaround by either adding additional checks in your script to see if it's up or adding delays. Thanks, Peter