How to Run and Verify the Deployment

This chapter explains how an end-user can run the Jenkins pipeline created in Chapter 8 and verify that the deployment to GKE completed successfully.

Running the Pipeline in Jenkins

  1. Open the Jenkins Dashboard.

  2. Click the job created earlier (e.g., EGL-GKE-Deployment).

  3. Click Build with Parameters.

You will now see the input parameters defined in Jenkinsfile & Pipeline Execution (GIT_BRANCH, IMAGE_TAG, WAR_FILE_PATH, etc.).

What to do now:

  • Provide the desired values for each parameter
  • (for example, update IMAGE_TAG when releasing a new version).
  • Click Build.

That’s all the end user needs — no duplication of the parameter list.

Monitoring the Pipeline Execution

Once the job starts:

  1. Click the build number (e.g., #17).

  2. Click Console Output.

You will see the pipeline moving through each stage:

  • Checkout
  • Build Docker image
  • Push to Artifact Registry
  • Deploy to GKE
  • Apply Kubernetes manifests

When everything succeeds, Jenkins prints: Pipeline completed successfully.

If something fails, this same page shows exactly which stage caused the issue.

Verifying the Deployment in GKE

After Jenkins applies your Kubernetes manifests, verify the Ingress:

kubectl get ingress myapp-ingress

Look for an EXTERNAL-IP value (example): 35.189.104.xx

This is the public entry point for your application.

Configure DNS (Optional)

If you want a custom domain (example): egldeployment.hcl-software.com

Create a DNS A record:

Name Type Value
egldeployment A 32.189.104.xx

After propagation, the application becomes accessible at: https://egldeployment.hcl-software.com

Final Verification in Browser

Open your browser and go to:

  • the Ingress IP address, or
  • the custom domain (if DNS is configured)

You should now see your deployed application running on GKE.