Go
Use a CI pipeline to build and test a Go application.
You can build and test a Go application using a Linux platform on Harness Cloud or a self-managed Kubernetes cluster build infrastructure.
This guide assumes you've created a Harness CI pipeline.
Install dependencies
If necessary, add a Run step to install any dependencies.
- step:
type: Run
identifier: dependencies
name: Dependencies
spec:
shell: Sh
command: |-
go get example.com/my-go-module- step:
type: Run
identifier: dependencies
name: Dependencies
spec:
connectorRef: YOUR_IMAGE_REGISTRY_CONNECTOR
image: golang:latest
command: |-
go get example.com/my-go-moduleCache dependencies
Add caching to your stage.
Cache your Go module dependencies with Cache Intelligence.
Add caching.enabled.true to your stage.spec:
- stage:
spec:
caching:
enabled: trueYou can use built-in steps to:
Build and run tests
Add Run steps to build and run your tests.
Visualize test results
You can view test results on the Tests tab of your pipeline executions. Test results must be in JUnit XML format.
You can use go-junit-report to output compatible JUnit XML reports.
For your pipeline to produce test reports, you need to modify the Run step that runs your tests. Make sure the command generates JUnit XML reports and add the reports specification.
Test splitting
You can use test splitting (parallelism) to improve test times.
Specify version
Go is pre-installed on Hosted Cloud runners. For details about all available tools and versions, go to Platforms and image specifications.
If your application requires a specific version of Go, add a Run step to install it.
Specify the desired Golang Docker image tag in your steps. There is no need for a separate install step when using Docker.
Full pipeline examples
The following full pipeline examples are based on the partial examples above.
If you copy this example, replace the placeholder values with appropriate values for your code repo connector and repository name. Depending on your project and organization, you may also need to replace projectIdentifier and orgIdentifier.
If you copy this example, replace the placeholder values with appropriate values for your code repo connector, Kubernetes cluster connector, Kubernetes namespace, and repository name. Depending on your project and organization, you may also need to replace projectIdentifier and orgIdentifier.
Next steps
Now that you have created a pipeline that builds and tests a Go app, you could:
Create triggers to automatically run your pipeline.
Add steps to build and upload artifacts.
Add a step to build and push an image to a Docker registry.
Last updated
Was this helpful?