Bitbucket Pipes digest: January 2021

[#1]

Pipes monthly digest January 2021

Hi,

Welcome to the next Bitbucket Pipes digest. This month comes packed with additions to Pipes. Don’t forget to subscribe (click Watch and select Articles)!

New pipes

bitbucket-pipe-release

atlassian/bitbucket-pipe-release:4.0.1

This pipe simplifies the release process of the Bitbucket Pipe or any Bitbucket Cloud project: publish docker image, commit and tag new git version of the pipe or other project.

- pipe: atlassian/bitbucket-pipe-release:4.0.1
  variables:
    DOCKERHUB_USERNAME: $DOCKERHUB_USERNAME
    DOCKERHUB_PASSWORD: $DOCKERHUB_PASSWORD
    IMAGE: 'myuser/my-awesome-image'

carbonetes-scan

carbonetes/carbonetes-scan:1.0.1
This pipe seamlessly integrates comprehensive container analysis directly into your CI/CD pipeline.

- pipe: carbonetes/carbonetes-scan:1.0.1
  variables:
    CARBONETES_USERNAME: $CARBONETES_USERNAME
    CARBONETES_PASSWORD: $CARBONETES_PASSWORD
    REGISTRY_URI: $REGISTRY_URI
    REPO_IMAGE_TAG: $REPO_IMAGE_TAG

Updated pipes

ssh-run

atlassian/ssh-run:0.3.0
Run a command or a bash script on your server.

Changes:

• Add support for ENV_VARS variable.

scp-deploy

atlassian/scp-deploy:1.0.0
Copy files to a remote server using SCP.

Changes:

• Changed EXTRA_ARGS parameter from string to array type in order to support better advanced use cases.

azure-aks-deploy

atlassian/azure-aks-deploy:1.0.1
A pipe that uses kubectl to interact with a Kubernetes cluster running on Azure Kubernetes Service

Changes:

• Introduced kubelogin as optional feature to get around interactive

kubectl-run

atlassian/kubectl-run:1.3.0
Run a command against a Kubernetes cluster. This pipe uses kubectl, a command line interface for running commands against Kubernetes clusters.

Changes:

• Add KUBECTL_APPLY_ARGS support. Allow to use -k kustomization flag.

anchore-scan

anchore/anchore-scan:0.2.11

Analyze and scan container image to produce software vulnerabilities, dockerfile and other security/compliance violations.

Changes:

• Bump version of inline scan to v0.9.0.

To discover more pipes, visit our Bitbucket Pipes Marketplace.

Top Community questions

• Ways-to-create-my-own-Pipe

• Problem with mkstemp permission

• How to push docker image tagged after git branch?

If you’d like help with Bitbucket Pipes, or you have an issue or feature request, let us know on Community.

[Jimmy Seddon]

This is a really cool update thanks @Halyna Berezovska!

[Gonchik Tsymzhitov]

@Halyna Berezovska  +1 That's great to see many improvements

[Nana Insaidoo]

@Halyna BerezovskaI recently found out that I can no longer contribute to the official-pipes registry as a result of this

NOTE: Currently we only accept contributions from trusted vendors who are the original author(s) or maintainers of the product / service the pipe integrates to.

Please how do you become a trusted vendor?

[Halyna Berezovska]

@Nana Insaidoo

You did right, Atlassian community or bitbucket pipelines channels are ways to communicate.

Right now we support trusted vendors to contribute. It means that if the pipe is, for example, deploying to Sonarcloud or Meterian etc., you have to work at Sonarcloud or Meterian company correspondingly, not just be the user of the tool.

However, if you did not signed the agreement, and you can confirm you work in vendor's company, we can accept your contributions as vendors, but someone has to contact you to sign the agreement. We will discuss your case inside the team. Thanks!

Regards, Galyna

[Nana Insaidoo]

@Halyna BerezovskaWell I can confirm I work at Meterian. As for the agreement, if you are talking about this one, I don't think it's accessible:

https://bitbucket.org/bitbucketpipelines/official-pipes/addon/bitbucket-contributor-agreement-add-on/sidebar-panel

The page never loads.

[bruno]

@Galyna Zholtkevych Bruno here, CTO @ Meterian. Please let us know what's the best way to authenticate ourselves. I can confirm that the agreement signing page keeps reloading.

[Halyna Berezovska]

@bruno @Nana Insaidoo thanks for contacting us.

We have discussed the case in the team - I informed agreement page is kind of broken.

You still should be able to contribute , just make pr, as you always did, and we will accept that.

Also I'll inform when the agreement page is fixed.

However, it should not block your PRs.

Regards, Galyna

[Nana Insaidoo]

@Halyna BerezovskaYou're right, I certainty confused some steps in the pipe review submission process. Creating a PR from our forked repository of the official pipes registry works. Thanks for the assistance!