Cloud customer?
Start for Free >
Upgrade in MyJFrog >
What's New in Cloud >


To construct a pipeline, you will need to learn the format, syntax, and facilities of the YAML-based Pipelines DSL.

Once JFrog Pipelines has been installed and configured for use, you can start building and running pipelines, for continuous integration and continuous delivery (CI/CD).

Pipelines are defined using Pipelines DSL, stored in one or more YAML files of key-value pairs, known as a pipeline config

The JFrog Platform provides the user interface for loading and viewing the pipeline config files you create, as well as for managing, viewing, and analyzing execution of your pipelines.

Page Contents

In This Section

This section provides information on how to use Pipelines DSL to create your pipelines.

  • Defining a Pipeline

    This page provides a high-level overview of the structure of a pipeline configuration file.

  • Pipelines Integrations

    An Integration connects Pipelines to an external service/tool. Each integration type defines the endpoint, credentials and any other configuration detail required for Pipelines to exchange information with the service. All credential information is encrypted and held in secure storage, in conformance with best security practices.

  • Pipelines Resources

    Resources are one of the key building blocks of all pipelines. They are information entities that are used for storing and exchanging information across steps and pipelines. 

    Resources are versioned and each version is immutable. They are also global and depending on the scope defined for the pipeline source, they can be available across pipelines, which enable you to connect multiple pipelines together to create a pipeline of pipelines.

  • Pipelines Steps

    Step is a unit of execution in a pipeline. It is triggered by some event and uses resources to perform an action as part of the pipeline.

  • Pipelines Utility Functions

    The Utility Functions are built-in shell functions that can be used in steps to interact with the runtime environment.

  • Pipelines Environment Variables

    This page describes the availability and usage of environment variables in pipelines.

  • Pipelines Tasks

    Pipelines Tasks enable developers to simplify and standardize CI/CD pipelines and help them reduce maintenance costs by promoting principles such as reusability, immutability, and versioning. 

    An ever-growing library of tasks are available out of the box and can be used in your pipeline definition. The same task can be invoked multiple times and can be executed across different steps in a pipeline. The code for each invoked task is stored in an Artifactory repository and downloaded/executed at the runtime of the step. In addition, since tasks are stored in Artifactory, they can be shared by different teams using local, remote, and virtual repositories. In fact, a task can be written in a way that leverages the Platform. 

  • Pipelines Templates

    Pipelines templates enable users to define templates for pipeline definitions and use these templates for creating pipelines.

  • No labels
Copyright © 2023 JFrog Ltd.