Igor Stoyanov Atlassian Team

@Markus Napp . Thank you you for your suggestion. It is already added in the variables description. FILENAME (*) - Name of the local file to upload. Supports glob patterns "*". e.g. *.html. Limit max 10 files, if limit reached - build fails. Accepts files only from BITBUCKET_CLONE_DIR or any subfolders in this path. Also…

@Paul S hi. You mean this one: bitbucket-dependency-scanner? Additionally here is the pipe link to repository. To discover more pipes: Bitbucket Pipes Regards, Igor

Hi @tochi . New version of the pipe released aws-eks-kubectl-run: Run command 'apply' with the assumed role user ARN. script: - pipe: atlassian/aws-eks-kubectl-run:3.0.0 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: $AWS_DEFAULT_REGION AWS_ROLE_ARN:…

Hi @prateek . In addition to @Theodora Boudale answer also you could try this pipe: Deploy a new service configuration script: - pipe: atlassian/aws-ecs-deploy:1.12.2 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY AWS_DEFAULT_REGION: 'us-east-1' CLUSTER_NAME: 'my-ecs-cluster'…

Hi @Maria S_ . To mention the author via slack username, please check this answer. Pipe allows you to use PAYLOAD_FILE, where you could add all the data supported by Slack Block Kit. Regards, Igor

Hi @Fletcher, Andrew . Good finding. The pipe bitbucket-pipe-release is open-sourced project, so if you want you may contribute to it. You are welcome to create a pull request, please follow the contribution page. Regards, Igor

@Atish Roy shuoldn't it flag the issue based on current commit of the code base. -- No. Why is it looking for obsolete code base and flagging issue? -- Because this secret still could be accessed by the hash commit. If the tool found your secret, then anyone else also could. If you think this is a false positive, you could…

@Fletcher, Andrew thank you for your investigation. Usually we use this option for git push: Configure repository ssh key pair and it will be safely used in pipeline to push to current repository and your investigation related to the case described by: if neither of above is configured, the http proxy and http origin will…

Hi @Atish Roy . You do not have problem with ms-teams-notify pipe. You have generated report from git-secrets-scan pipe, in which you have the information that you exposed your WEBHOOK_URL value in previous commits. You have a fingerprint for commit in annotation so you could check this. Regards, Igor

@Atish Roy Please provide your bitbucketpipelines.yml config and result log outputs. Regards, Igor

Hi @Atish Roy . Thanks for your question. Did you create WEBHOOK_URL Repository variable as a secured variable? Regards, Igor

Hi @Sathish Kumar Reddy . Thanks for your question. Please provide more details with your configuration from bitbucket-pipelines.yml and copy log output in text format (delete all sensitive data). Regards, Igor

Hi @Julien HENRY . Thanks for your question. We will discuss this with Bitbucket Pipelines team and notify you. Regards, Igor

Hi @tochi . The reason could be that aws-ecr-push-image supports assuming role-arn, but aws-eks-kubectl-run currently not. We will add this feature to aws-eks-kubectl-run pipe and notify you when new version will be released. Regards, Igor

Hi @Julien HENRY . I think, this pipe is required to sue python image by default. Please, try to add: image: python:3.10 to your release step. Waiting for your feedback. Regards, Igor

Hi @moritz_matchory_com . Try to add DOCKER_HOST to your pipe variables: example. Regards, Igor

Hi @Leandro Casanovas . Did you build image with required tag first according to docs? Check this example: script: # build the image - docker build -t my-docker-image:1.2.3-RC2 . # use the pipe to push the image to AWS ECR - pipe: atlassian/aws-ecr-push-image:2.4.2 variables: AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID…

@moritz_matchory_com hi. Try to connect to your service container without pipe usage, just on pipelines level to determine where is the problem. Maybe the problem is with your configuration. Regards, Igor

@Curtis hi. We released a new pipe jsm-ops-send-alert. Example: script: - pipe: atlassian/jsm-ops-send-alert:0.1.0 variables: JSM_API_TOKEN: $JSM_API_TOKEN JSM_CLOUD_ID: $JSM_CLOUD_ID JSM_USER_EMAIL: $JSM_USER_EMAIL MESSAGE: 'Hello, world!' You could try it, waiting for your feedback. Regards, Igor 

@Andrew Klossner . Try to run your trigger pipeline step without this step previously executed `name: Deploy to AWS account`. Maybe the reason is there because you changed docker infra here `source "$HOME/setup-docker.bash" local` Regards, Igor

Hi @Andrew Klossner . Try to add services docker to your script as described on this page: run-docker-commands-in-bitbucket-pipelines If you use self-hosted runners, check this community question Regards, Igor

Hi @b.lagerweij . Thanks for your feature request. We will think about adding support of pre-execution script, so will have the ability to implement your custom logic before the pipe execution. We will notify you when this feature will become available. Regards, Igor

Hi @Andrew Klossner . Thanks for question. Do you still have this issue. If yes: provide us please with full pipelines config file and output logs. Regards, Igor

@Fredrik Svärd hi. Thank you for your question. According to your logs <span>DEBUG: <a href="https://api.bitbucket.org/" rel="noopener nofollow noreferrer" target="_blank">https://api.bitbucket.org:443</a> "POST /2.0/repositories///downloads HTTP/11" 403 57</span>93 Seems like you do not have environment…

Hi @Katie Schmidt . Thanks for your question. Currently, there is no implemented pipe for MS Fabric. If you’d like to suggest a pipe to be improved or new pipe to be implemented, please, find the appropriate ticket in the list of existing tickets , vote for them or create a new suggestion request with…

@Nino Gresenz hi. We updated an example you suggested in the pipe README. Regards, Igor

Hi @Aliaksandr Prytychanka . The error you provided points you with Invalid URL '' (empty string). Check/update the repository variable $WEBHOOK_URL you used in the pipe. Regards, Igor

@Curtis : please take a look at this question. Also according to this page: * Opsgenie APIs will continue to work even while you move to Jira Service Management. However, once you complete your move, we recommend that you start using the Jira Service Management Ops REST API. Answering your question about alerts to Jira Ops…

rajputj3@bv.com , @Syahrul : this pipe is maintained by atlassian Bitbucket Pipelines Pipes Team and under the hood executes the next command: az webapp deployment source config-zip <parameters>. So to understand what to deploy rajputj3@bv.com : you should read the docs and provide correct zip archive. @Syahrul : this pipe…

@Curtis , thanks for your question. We are investigating this now and we will notify you. Regards, Igor