Before You Begin

This 10-minute tutorial shows you how to configure a pipeline to automate and build a Docker image of a Node.js microservice, push it to Oracle Cloud Infrastructure Registry (OCIR), and then deploy the Docker image to OCI Container Engine for Kubernetes (OKE) using Oracle Visual Builder Studio (VB Studio).

Background

In VB Studio, you can create a build pipeline to define dependencies of jobs and create a path or a chain of builds. You define a pipeline either using a pipeline designer or through YAML (YAML Ain't Markup Language) script, a human-readable data serialization language that is commonly used for configuration files.

In this tutorial, you'll create a pipeline using YAML that does the following:

• Runs a build of the job that creates the Docker image of the Node.js microservice and pushes it to Oracle Cloud Infrastructure Registry (OCIR)
• Runs a build of the job that deletes the microservice objects from Oracle Container Engine for Kubernetes (OKE). If the microservice is already deployed, the job is successful. If the microservice isn't deployed, the job fails.
• Runs a build of the job that deploys the Docker image to OKE, irrespective of the undeploy job's build status

What Do You Need?

• A web browser
• Your Oracle Cloud account credentials
• The Docker, Node.js, and Kubernetes VM template configured in the previous tutorial. The jobs you'll add in the pipeline use this Build VM template.

  

• The build job you created in this tutorial to build the Docker image and push it to OCIR

  If you changed the job's name in the tutorial, enter the new name here:

  Build Job Name

• The deploy and undeploy jobs you created in this tutorial to deploy and undeploy the Node.js microservice objects from OKE

  If you changed the job names in the tutorial, enter the new names here:

  Deploy Job Name

  Undeploy Job Name

Create a Pipeline File using YAML

1. Open the VB Studio project.
2. In the left navigation menu, click Git.
3. From the Repositories list, select my-nodejs-app.
4. Click + File.

   

5. In File Name, enter .ci-build/pipeline.yml.

   All YAML files must reside in the .ci-build directory in the root directory of a hosted Git repository's master branch. Within the .ci-build directory, a job or a pipeline configuration file must be saved with the extension .yml.

6. In the content area, copy and paste this script.
   Click to copy the script.

   pipeline:
     name: build-deploy-pipeline-yaml
     auto-start: false
     start:
     - 
     - 
     - on succeed, fail:
       - 

   The above script performs these actions:

   • Sets the pipeline's name to build-deploy-pipeline-yaml
   • Sets auto-start to false. This is required to disable pipeline's builds if its jobs are triggered externally (outside the pipeline).
   • Defines the order of builds as:
     1. Run a job's build
     2. Run a job's build
        The undeploy job deletes Kubernetes objects deployed to OKE. If the objects exist, the job is successful. If the objects don't exist, the job fails.
     3. Run a job's build
        By default, if a job's build fails in a pipeline, VB Studio stops the pipeline's builds immediately and doesn't progress to the next job. Using the on succeed, fail condition, you've configured the pipeline to progress to the next job irrespective of the previous job's build status.
7. Click Commit.
8. In the Commit Changes dialog box, click Commit.

Run the Pipeline

1. In the left navigation menu, click Builds.
2. Click the Pipelines tab and verify the pipeline.

   

3. In the build-deploy-pipeline-yaml pipeline's box, click Build .
4. Click the pipeline's build-deploy-pipeline-yaml name.
5. On the pipeline's instances page, monitor its builds.

   If the service and deployment objects exist on OKE, builds of all jobs are successful. Your pipeline instance should look like this:

   

   If the service and deployment objects don't exist on OKE, the job's build fails and the pipeline progresses to the next job. Your pipeline instance should look like this:

   

6. To get the deployed microservice's URL, click the job's build link.
7. On the build's details page, click Build Log to see the build's log and the deployed microservice's URL.