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. For instructions, go to:

• View test reports on the Artifacts tab.
• View code coverage reports on the Artifacts tab.
• View GCS artifacts on the Artifacts tab.
• View JFrog artifacts on the Artifacts tab.
• View Sonatype Nexus artifacts on the Artifacts tab.
• View S3 artifacts on 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.

• With Harness Cloud build infrastructure, use the GitHub Action step.
• With other build infrastructures, use the GitHub Actions Drone plugin in a Plugin step.

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.