Skip to main content

Explore plugins

Plugins perform predefined tasks. They are essentially templated scripts that can be written in any programming language.

You can build your own plugins or use one of the many preexisting plugins from the Drone Plugins Marketplace, GitHub Actions Marketplace, or the Bitrise Integrations library.

To include a plugin in a CI pipeline, you use either the generic Plugin step or a specialized plugin step.

Custom plugins

You can write your own plugins and use Plugin steps to run them in your Harness CI pipelines.

Drone plugins

You can use Plugin steps to run Drone plugins in Harness CI pipelines.

For example, you can use the Artifact Metadata Publisher plugin to publish any artifact URL to the Artifacts tab.

Bitrise integrations

How you run Bitrise integrations in Harness CI pipelines depends on your build infrastructure.

  • With Harness Cloud build infrastructure, use the Bitrise step.
  • With other build infrastructures, you can use a custom plugin.

GitHub Actions

How you run GitHub Actions in Harness CI pipelines depends on your build infrastructure.

Jira integrations

If you want your CI pipelines to update Jira issues, you can use a Plugin step as explained in Integrate Jira in a CI pipeline.

Scanner integrations

The Harness Security Testing Orchestration module provides first-class support for many security scanners. You can also use the Drone SonarScanner plugin in a Plugin step, for example:

              - step:
type: Plugin
name: Plugin_1
identifier: Plugin_1
spec:
connectorRef: YOUR_DOCKER_CONNECTOR_ID
image: kytay/sonar-node-plugin ## This is the sonarscanner plugin image.
settings:
sonar_host:
from_secret: sonar_host
sonar_token:
from_secret: sonar_token
use_node_version: 16.18.1

For information about SonarScanner plugin settings, go to the Drone SonarScanner plugin documentation.

For information about the Plugin step settings, go to the Plugin step settings documentation.