Add Collaboration Providers

The following Collaboration Providers are covered here:

To collaborate and share the information in Harness with other users, add a Collaboration Provider.

  1. Click Setup.
  2. Click Connectors.
  3. Click Collaboration Providers.
  4. Click Add Collaboration Provider.
  5. In Type, click the collaboration provider type.
  6. In Host, enter the URL or Webhook of the provider.
  7. In Display Name, enter a name for the collaboration provider.
    If you want to restrict the use of a provider to specific applications and environments, do the following:
  8. In Usage Scope, click the drop-down under Applications, and click the name of the application.
  9. In Environments, click the name of the environment.
  10. Click SUBMIT.

SMTP

Configuring your SMTP server is required only if you are using Harness On-Prem, or if you are using Harness SaaS and wish to use your own SMTP server instead of the Harness SaaS default SMTP option. For information on notifications, see User Notifications and Alert Settings.

The SMTP dialog has the following fields.

Field

Description

Host

The URL of the SMTP server.

Port

The port number the SMTP server is listening on (typically, 25).

From Address

Enter the email address that Harness will use to send emails.

Username

Enter the username for the email account.

Password

Enter the password for the email account.

Display Name

Enter a display name for the provider.

Usage Scope

If you want to restrict the use of a provider to specific applications and environments, do the following:

  1. In Usage Scope, click the drop-down under Applications, and click the name of the application.
  2. In Environments, click the name of the environment.

Slack

Once you add Slack as a Collaboration provider, you can use Slack to notify users of Harness activity. For information on using Slack for notifications, User Notifications and Alert Settings.

The Slack dialog has the following fields.

Field

Description

Display Name

Enter the name of the Slack channel to post notifications. If left empty, then the default channel from the Webhook URL is used.

Slack Webhook URL

To find your Webhook information, see Incoming Webhooks from Slack.

Usage Scope

If you want to restrict the use of a provider to specific applications and environments, do the following:

  1. In Usage Scope, click the drop-down under Applications, and click the name of the application.
  2. In Environments, click the name of the environment.
You will be asked to choose a channel (or create a new one) for incoming Harness notifications. If you would like to send notifications from Harness to multiple channels (for example, failed deployments to channel A, successful deployments to channel B), you can define this under the Harness Notification Groups settings. See User Notifications and Alert Settings.

Jira

For steps on using Jira in a Workflow or Pipeline, see Jira Integration.

Atlassian Jira provides dev teams with project management and issue tracking throughout the software delivery lifecycle. Harness integrates with Jira to enable you to track the progress of deployments by creating and updating Jira issues from Harness, and approve deployment stages using Jira issues as part of Workflow and Pipeline approvals. Your Jira account is integrated into Harness as a Collaboration Provider.

The Jira dialog has the following fields.

  • Display Name - Enter a name to identify this Jira account connection. When you add Jira steps to Workflow or Pipelines, you will select the Jira account to use by selecting this display name.
  • Base URL - Enter the Base URL which your Jira users use to access your Jira applications, such as https://mycompany.atlassian.net. In Jira, the base URL is set to the same URL used Web browsers to viewing your Jira instance. For more information, see Configuring the Base URL from Atlassian.
  • Username - Enter the username of the Jira account to use for the connection.
  • Password/API Token - Enter the password or API Token to use for the account. For more information, see API tokens from Atlassian.

ServiceNow

For information on using your ServiceNow Collaboration Provider in Workflows and Pipelines, see ServiceNow Integration.

Using ServiceNow tickets, you can track/audit the progress of Harness deployments (and Pipelines) and approve/reject Pipeline stages or Workflows.

The ServiceNow dialog has the following fields.

  • Display Name - Enter a name to identify this ServiceNow account connection. When you add ServiceNow steps to Workflow or Pipelines, you will select the ServiceNow account to use by selecting this display name.
  • Base URL - Enter the Base URL which your ServiceNow users use to access ServiceNow, such as https://example.service-now.com/.
  • Username - Enter the username of the ServiceNow account to use for the connection.
  • Password - Enter the password to use for the account.


How did we do?