Recently Viewed Topics
Before You Begin
These instructions describe how to push a Docker image from Jenkins to Tenable.io Container Security.
These steps assume you are already comfortable using Jenkins and are already pushing Docker images to a public or private registry. If you are already using Jenkins, but have not built Docker container images, familiarize yourself with the documentation for the Jenkins CloudBees Docker Build and Publish plugin.
- Log in to Jenkins.
- Click Manage Jenkins, then click Manage Plugins.
A list of installed plugins appears.
- Click Available.
- In the Filter box, enter CloudBees Docker Build and Publish plugin.
- Select the check box that corresponds to the plugin.
Install the plugin.
The CloudBees Docker Build and Publish plugin is installed and ready for use by Jenkins jobs.
- On the Jenkins dashboard, select the job you want to modify.
- Click Configure.
- In the Build section, click Add build step.
- In the drop down box, select Docker Build and Publish.
- Enter the details for the following configuration parameters:
- Repository Name: The repository name and image name. For example, if you are building a rabbitmq container image, you can name the repository rabbitmq and the image rabbitmq. In this example, in the Repository Name box, you will type rabbitmq/rabbitmq.
- Tag: The tag name. The simplest tag name to use is latest.
- Docker Host URI: The Jenkins path to the Docker Host. If the Docker Host is running on localhost, then in the Docker Host URI box, enter tcp://127.0.0.1:4243.
- Docker registry URL: The Tenable.io Container Security API endpoint, which in this case is https://cloud.flawcheck.com.
Registry credentials: The registry credentials that you select from the box.If you have not added registry credentials, click here for instructions on how to do so.
- Click Add.
- Click Username with password.
- In the Username box, enter your Tenable.io Container Security user name.
- In the Password box, enter your Tenable.io Container Security password.
The credentials are added.
Jenkins builds will now be sent to Tenable.io Container Security for storage, distribution, vulnerability scanning, and malicious code scanning.