Skip to main content

Traditional Deployments (SSH) Overview

Traditional deployments use application package files and a runtime environment (Tomcat, JBoss) in Harness.

For How-tos on Traditional deployments, see Traditional (SSH) Deployments How-tos.You can perform traditional deployments to AWS and Azure, and to any server on any platform via a platform agnostic Physical Data Center connection. In all cases, you simply set up a Harness Infrastructure Definition and target the hosts on the platform.

These deployments are different from Harness deployments using container orchestration platforms like Kubernetes, Helm, Pivotal, AWS ECS, and Azure.

For a Build and Deploy Pipeline using a Traditional deployment, see Artifact Build and Deploy Pipelines Overview.Traditional deployments involve obtaining an application package from an artifact source, such as a WAR file in an AWS S3 bucket, and deploying it to a target host, such as a virtual machine.

Supported Packaging Formats​

Harness supports the following traditional deployment packaging formats: WAR, JAR, TAR, RPM, ZIP, Docker, and custom files.

All of these formats are also supported by other Harness deployment types, such as Kubernetes, Helm, PCF, ECS, etc.  This guide is concerned with traditional deployments outside of the container orchestration platforms.

Supported Platforms and Technologies​

See SSH in Supported Platforms and Technologies.

Deployment Summary​

For a general overview of how Harness works, see Harness Key Concepts.

The following list describes the major steps involved in a Traditional deployment:

  1. Installing the Harness Delegate in your target infrastructure. See Harness Delegate Overview.
  2. Add a connection to your artifact server. See Add Artifactory Servers.
  3. Add a connection to your cloud provider. This is a connection to your deployment infrastructure, either physical or hosted in a cloud platform like AWS, GCP, or Azure. See Add Cloud Providers.
  4. Create the Harness Application for your deploying your application packages.
  5. Create the Harness Service using the SSH type.
    1. Add your packaged application file(s) as an Artifact Source.
  6. Create the Harness Environment containing the Infrastructure Definition definition of your deployment infrastructure.
  7. Create the Basic Deployment Workflow.
  8. Deploy the Workflow.
  9. Next steps:
    1. Create a Harness Pipeline for your deployment, including Workflows and Approval steps. For more information, see Pipelines and Approvals.
    2. Create a Harness Trigger to automatically deploy your Workflows or Pipeline according to your criteria. For more information, see Triggers.
    3. Create Harness Infrastructure Provisioners for your deployment environments. For more information, see Infrastructure Provisioners.

Next Step​

Traditional Deployments How-tos: