Build, test, and publish a Docker Image for a Java HTTP server application
In this tutorial, you will create a Harness CI pipeline for a Java HTTP server application that does the following:
- Build and test the application.
- Publish a Docker image.
- Pull the published Docker image, then pull and run it as a Background step.
- Run a connectivity test against the running application.
If you don't have a Harness account yet, you can create one for free at app.harness.io.
Create your pipeline
- Fork the repository https://github.com/keen-software/jhttp into your GitHub account.
- Follow the Get Started wizard in Harness CI.
- New account
- Existing account
Sign up for a new Harness account. Select the Continuous Integration module after your initial sign in. This brings you to the Get Started wizard.
Log in to your Harness account. You can either create a new project or select an existing project, and then select the Continuous Integration module. In the Project pane, expand the Project Setup menu, and then select Get Started.
- When you are prompted to select a repository, search for jhttp, select the repository that you forked in the earlier step, and then select Configure Pipeline.
- Select Starter Pipeline, and then select Create Pipeline.
Docker Hub connector
You need a Docker Hub connector. This connector is used to authenticate and publish the Java HTTP server image to your Docker Hub account.
If you have not created a Docker Hub connector yet, follow these steps.
Create connector
- From the left pane, expand the Project Setup, and then select Connectors.
- Select + New Connector, and then select Docker Registry.
- In the Name field, enter Docker Hub, and then select Continue.
- In the Docker Registry URL field, enter https://index.docker.io/v2/.
- For Provider Type, select DockerHub.
- In the Username field, enter your Docker Hub username.
- In the Password field, select Create or Select a Secret. Follow the prompts to add your Docker Hub access token, and then click Continue.
- At the next screen, select Connect through Harness Platform, and then select Save and Continue.
- After Harness performs a validation test, select Finish.
- In your list of connectors, note the ID of the connector that you just created. If you named the connector
Docker Hub, the ID should beDocker_Hub.
Your connector needs an access token with Read, Write, Delete permissions.
Modify the pipeline
From the left pane, select Pipelines, and then select your jhttp pipeline from the list.
Switch from the Visual view to the YAML view, and then select Edit YAML.
A starter pipeline is created with a single stage. It should look similar to this:
pipeline:
name: Build jhttp
identifier: Build_jhttp
orgIdentifier: default
stages:
- stage:
name: Build
identifier: Build
type: CI
spec:
cloneCodebase: true
execution:
steps:
- step:
type: Run
name: Echo Welcome Message
identifier: Run
spec:
shell: Sh
command: echo "Welcome to Harness CI"
platform:
os: Linux
arch: Amd64
runtime:
type: Cloud
spec: {}
properties:
ci:
codebase:
connectorRef: account.Github_OAuth
repoName: your_user/jhttp
build: <+input>
Replace the sample stages section with the following variables and stages sections:
variables:
- name: DOCKERHUB_USERNAME
type: String
description: Your Docker Hub username
value: <+input>
stages:
- stage:
name: Build
identifier: Build
type: CI
spec:
cloneCodebase: true
execution:
steps:
- step:
type: RunTests
name: Run Tests
identifier: RunTests
spec:
connectorRef: Docker_Hub
image: maven:3.5.2-jdk-8-alpine
language: Java
buildTool: Maven
args: test
packages: io.harness.
runOnlySelectedTests: true
postCommand: mvn package -DskipTests
reports:
type: JUnit
spec:
paths:
- "**/*.xml"
timeout: 30m
- step:
type: BuildAndPushDockerRegistry
name: Build and Push an image to Docker Registry
identifier: BuildandPushanimagetoDockerRegistry
spec:
connectorRef: Docker_Hub
repo: <+pipeline.variables.DOCKERHUB_USERNAME>/jhttp
tags:
- <+pipeline.sequenceId>
platform:
os: Linux
arch: Amd64
runtime:
type: Cloud
spec: {}
- stage:
name: Run Connectivity Test
identifier: Run_Connectivity_Test
description: ""
type: CI
spec:
cloneCodebase: false
platform:
os: Linux
arch: Amd64
runtime:
type: Cloud
spec: {}
execution:
steps:
- step:
type: Background
name: Run Java HTTP Server
identifier: Run_Java_HTTP_Server
spec:
connectorRef: Docker_Hub
image: <+pipeline.variables.DOCKERHUB_USERNAME>/jhttp:<+pipeline.sequenceId>
shell: Sh
portBindings:
"8888": "8888"
- step:
type: Run
name: Test Connection to Java HTTP Server
identifier: Test_Connection_to_Java_HTTP_Server
spec:
shell: Sh
command: |-
until curl --max-time 1 http://localhost:8888; do
sleep 2;
done
This configuration requires the Docker Hub connector ID to be Docker_Hub. If your connector ID is different, replace Docker_Hub with the correct ID.
Select Save in the YAML editor.
Run your pipeline
In the Pipeline Studio, select Run.
Enter your Docker Hub username in the
DOCKERHUB_USERNAMEfield.In the Build Type field, select Git Branch, and then enter main in the Branch Name field.
Select Run Pipeline.
Observe each step of the pipeline execution. When the first stage completes, test results appear on the Tests tab.
When the second stage completes, you should see the successful
curlcommand in the Test Connection to Java HTTP Server step.
For a comprehensive guide on application testing, Harness provides O'Reilly's Full Stack Testing book for free at https://harness.io/resources/oreilly-full-stack-testing.