Application Scanning in your pipeline
The bitbucket-pipelines.yml defines your Pipelines builds configuration. If you're new to Pipelines you can learn more about how to get started here.
In this workshop, we have provided you with a sample bitbucket-pipelines.yml file containing distinct steps mapped to our workflow:
  • Build the code
  • Build the docker image
  • Scan the container image
  • Deploy the container image to a registry
  • Deploy the container image to a Kubernetes cluster
Let's start by examining the first steps to build the code and container:
image: atlassian/default-image:2
build-app: &build-app
- step:
name: Build and Test
- maven
- mvn -B verify --file pom.xml
# Collect checkstyle results, if any, and convert to Bitbucket Code Insights.
- pipe: atlassian/checkstyle-report:0.2.0
atlassian-security-scan: &atlassian-security-scan
- step:
name: Security Scan
# Run a security scan for sensitive data.
# See more security tools at
- pipe: atlassian/git-secrets-scan:0.4.3
In this example, we perform a few activities to illustrate a representative pipeline. The first stage is build-app, and it's primary purpose is to run a maven build with checkstyle to generate a jar file. The next stage is entitled atlassian-security-scan and we utilize the Atlassian pipe to scan for git secrets. These two steps are include for convenience and illustrative of a best practice to ensure things are working. We will not cover their details in the workshop, and we encourage you to review if you are interested.
The next block includes Snyk scan where we use two pipes to scan and push an image.
snyk-scan-push-image: &snyk-scan-push-image
- step:
name: "Push container image"
- docker
- docker build -t $IMAGE .
- docker tag $IMAGE $IMAGE:latest
- pipe: snyk/snyk-scan:0.5.1
LANGUAGE: "docker"
TARGET_FILE: "Dockerfile"
MONITOR: "true"
- pipe: atlassian/aws-ecr-push-image:1.1.3
TAGS: latest
The first part of the script builds the docker image with commands already familiar to docker users.
The next block is the Snyk Scan pipe for Atlassian Bitbuckets, with configuration parameters. The details for configuring the pipe are available online, but you can see the human-readable names help us easily understand what is going on. Let's take a closer look at a few of these:
  1. 1.
    SNYK_TOKEN is being passed into our pipe as a repository variable previously defined in the [Bitbucket Configuration]() module.
  2. 2.
    PROJECT_FOLDER is the folder in which the project resides and normally defaults to .. However, in our example, we have set this to app/goof and
    are passing this as an artifact to other steps in our pipeline.
  3. 3.
    CODE_INSIGHTS_RESULTS defaults to false. However, we will want to create Code Insight report with Snyk test results so we have set this to true.
  4. 4.
    SEVERITY_THRESHOLD reports on issues equal or higher of the provided level. The default is low but in our case, we are interested only in high so we have defined this variable accordingly.
  5. 5.
    DONT_BREAK_BUILD the default is false and this is to be expected. Under normal circumstances we would want to break our build if issues our found. However, for the purpose of this workshop we set the value to true.
You can run Snyk security scans on your pull requests and view results in Code Insights with the help of a brand new Snyk Security Connect App on the Atlassian Marketplace. It's easy to get started and you can install the app with just a few clicks.
The last block is for an EKS deployment. We include the block in the workshop to complete the picture of a deployment to a destination environment. The pipeline will automatically deploy the container to the named pipeline based on the declarations below.
deploy-image: &deploy-image
- step:
name: "Push container image"
- pipe: atlassian/aws-eks-kubectl-run:2.2.0
Export as PDF
Copy link
Edit on GitHub