BitBucket Pipelines migration
For users of snyk/snyk-scan
< v1.0.0
snyk/snyk-scan
< v1.0.0snyk/snyk-scan
<v1.0.0 uses Snyk CLI Images. As all Snyk CLI Images will be removed, snyk/snyk-scan
< v1.0.0 will stop working also.
See the upgrade guide in Snyk Docs to upgrade to snyk/snyk-scan
>= v1.0.0
For users of snyk/snyk-scan
>= v1.0.0
snyk/snyk-scan
>= v1.0.0Create your own custom image
Users can create their own custom images to use. This option is available for snyk/snyk-scan
>= v1.0.0 only. For details, see User-defined custom images for CLI.
Creating a custom image should guarantee compatibility with your system. However, there are alternative images to which you can upgrade if creating a custom image is not possible.
Upgrade to a supported Snyk Image
After you have validated that you are using a Snyk Image that will be removed, as outlined for users of snyk/snyk-scan
< v1.0.0, refer to the Snyk images migration guidelines to view upgrade paths for your configuration.
An example follows of upgrading to a supported Snyk Image.
In the example bitbucket-pipeline.yml
configuration that follows, a Snyk image is configured that will be removed on 12 Aug 2024:
Following the Snyk images migration guidelines, you can upgrade to a supported Snyk Image as shown here:
Download and install Snyk CLI directly
If you do not want to use the Bitbucket snyk/snyk-scan
integration, you have the option to install and use the Snyk CLI directly.
The following example shows using the CLI directly.
In the example bitbucket-pipeline.yml
configuration that follows, a pipeline is configured that does the following:
Downloads the CLI
Validates the CLI with a SHASUM check
Runs the CLI to test the code
Last updated
Was this helpful?