Skip to main content

Run a Sauce Connect Proxy service

In Harness CI, you use Background steps to manage services that need to run for the entire lifetime of a Build stage. To demonstrate how you can use Background steps, this topic explains how to run Sauce Connect Proxy in a Background step. Sauce Labs is a web and mobile application automated testing platform. Sauce Connect Proxy can run as a Background step in your Harness CI pipeline, and act as a proxy server between a Sauce Labs infrastructure and your CI pipeline.

Add a Background step

  1. Create a Harness text secret containing a Sauce Labs Access Key. Make note of the secret's ID.

  2. Create a Harness CI pipeline and add a Build stage.

    You can disable clone codebase, because the pipeline created in this example doesn't need to pull any source code.

  3. You can use Background steps with any build infrastructure. To follow along with this example, use either Harness Cloud build infrastructure or a Kubernetes cluster build infrastructure.

  4. Add a Background step configured as follows:

    • Name: Enter a name, such as sauce_connect.
    • Container Registry: Select a Docker connector.
    • Image: Enter the name and tag of a Sauce Connect Docker image, such as saucelabs/sauce-connect:latest.
    • Environment Variables: Add two environment variables for your Sauce Labs credentials:
    • Port Bindings: If you chose Harness Cloud build infrastructure, add port bindings "8032": "8032". For more information, go to Background step settings - Port bindings.
  5. Select Apply Changes to save the Background step.

Add a health check

Harness recommends adding health checks for Background steps. This example runs a cURL command to poll the readiness of the Sauce Connect service until it returns a successful response. This ensures that Sauce Connect is ready to receive traffic before the pipeline continues.

In your pipeline's Build stage, after the Background step, add a Run step configured as follows:

  • Name: Enter a name, such as wait for SC.
  • Container Registry and Image: With a Kubernetes cluster build infrastructure, select a Docker connector and enter the image curlimages/curl:7.83.1. With Harness Cloud, these are not required because Harness Cloud runners already have the required cURL binary.
  • Shell: Select Bash
  • Command: Enter the following:
until [ "$(curl -s -o /dev/null -w ''%{http_code}'' localhost:8032/readiness)" == "200" ]
sleep 2
echo "SC ready"

Run the pipeline

Save the pipeline, select Run, and then select Run Pipeline.

While the build runs, you can observe the logs. When Sauce Connect is ready, the health check step prints SC ready.

YAML example

Here's the YAML for the Build stage created in this topic. A complete Harness CI pipeline would have additional steps after the Run step that build code, run tests, push images, and so on. Some or all of these steps might interact with the Sauce Labs Proxy service running in the background.

- stage:
name: build
identifier: build
description: ""
type: CI
cloneCodebase: false ## Clone codebase is disabled for this example.
platform: ## This stage uses Harness Cloud build infrastructure.
os: Linux
arch: Amd64
type: Cloud
spec: {}
- step: ## Background step runs the Sauce Connect Docker image.
type: Background
name: Sauce Connect
identifier: Sauce_Connect
connectorRef: account.harnessImage
image: saucelabs/sauce-connect
shell: Sh
SAUCE_ACCESS_KEY: <+secrets.getValue('Sauce_Access_Key')>
"8032": "8032"
- step: ## Run step checks that Sauce Connect is healthy before allowing other steps to run.
type: Run
name: Wait for SC
identifier: Wait_for_SC
shell: Bash
command: |-
until [ "$(curl -s -o /dev/null -w ''%{http_code}'' localhost:8032/readiness)" == "200" ]
sleep 2
echo "SC ready"