JFrog Pipelines
Published: 2020-04-06 07:11:54


# What is JFrog Pipelines? 

JFrog Pipelines is one of the most advanced DevOps automation solutions in Today's world to perform end-to-end automation tasks of building, testing, and deploying software as part of a system of (CI/CD).

Some Important concept of [JFrog Pipelines](https://jfrog.com/pipelines/)

#Steps
 
Steps are executable units that perform a specific task, such as building an application, pushing to an artifactory, Docker, AWS, GoogleCloud, etc. provisioning the machine on ubuntu_16.04, ubuntu_18.04, CentOS_7 and windowServer_2019, etc.

#Resource

Resource typically contains information needed for a step in a pipeline to execute and can also be used to store information produced by a step. For example source code control system (Git Repository ), Image, FileSpec, HelmChart etc.
The available resource for Jfrog Pipelines are:
[Aql](https://www.jfrog.com/confluence/display/CICD/Aql), [BuildInfo](https://www.jfrog.com/confluence/display/CICD/BuildInfo), [DistributionRule](https://www.jfrog.com/confluence/display/CICD/DistributionRule), [FileSpec](https://www.jfrog.com/confluence/display/CICD/FileSpec), [GitRepo](https://www.jfrog.com/confluence/display/CICD/GitRepo), [Image](https://www.jfrog.com/confluence/display/CICD/Image) , [ReleaseBundle](https://www.jfrog.com/confluence/display/CICD/ReleaseBundle), [RemoteFile](https://www.jfrog.com/confluence/display/CICD/RemoteFile), [VmCluster](https://www.jfrog.com/confluence/display/CICD/VmCluster) and [Webhook](https://www.jfrog.com/confluence/display/CICD/Webhook). 

#Integrations

Integrations are used to connect your Pipelines workflows to third party platforms or services and manage secrets like tokens, passwords, configuration detail that are needed for Steps in a Pipeline to interact with the source.
All credential information is encrypted and maintained separately from the pipeline definition, and held in a secure storage.

The available integration types for Jfrog Pipelines are:
[Airbrake](https://www.jfrog.com/confluence/display/CICD/Airbrake+Integration), [Artifactory](https://www.jfrog.com/confluence/display/CICD/Artifactory+Integration), [AWS Keys](https://www.jfrog.com/confluence/display/CICD/AWS+Keys+Integration), [Azure Keys](https://www.jfrog.com/confluence/display/CICD/Azure+Keys+Integration), [Bitbucket](https://www.jfrog.com/confluence/display/CICD/Bitbucket+Integration), [Digital Ocean](https://www.jfrog.com/confluence/display/CICD/Digital+Ocean+Integration), [Distribution](https://www.jfrog.com/confluence/display/CICD/Distribution+Integration), [Docker Registry](https://www.jfrog.com/confluence/display/CICD/Docker+Registry+Integration), [External Webhook](https://www.jfrog.com/confluence/display/CICD/External+Webhook+Integration), [File Server](https://www.jfrog.com/confluence/display/CICD/File+Server+Integration), [Generic](https://www.jfrog.com/confluence/display/CICD/Generic+Integration), [Github Enterprise](https://www.jfrog.com/confluence/display/CICD/GitHub+Enterprise+Integration), [Github](https://www.jfrog.com/confluence/display/CICD/GitHub+Integration), [Gitlab](https://www.jfrog.com/confluence/display/CICD/GitLab+Integration), [Google Cloud](https://www.jfrog.com/confluence/display/CICD/Google+Cloud+Integration), [Internal Webhook](https://www.jfrog.com/confluence/display/CICD/Internal+Webhook+Integration), [Jira](https://www.jfrog.com/confluence/display/CICD/Jira+Integration), [Kubernetes](https://www.jfrog.com/confluence/display/CICD/Kubernetes+Integration), [Newrelic](https://www.jfrog.com/confluence/display/CICD/NewRelic+Integration), [PEM Key](https://www.jfrog.com/confluence/display/CICD/PEM+Key+Integration), [Slack](https://www.jfrog.com/confluence/display/CICD/Slack+Integration), [SMTP Credentials](https://www.jfrog.com/confluence/display/CICD/SMTP+Credentials+Integration) and [SSH Key](https://www.jfrog.com/confluence/display/CICD/SSH+Key+Integration).

#Pipelines   

Pipelines is a collection of interconnected series and parallel steps to achieve an outcome.

#Run
 
Run is an instance of Pipelines execution. The Pipeline Run Logs view of Pipelines provides the facilities to view the log of execution, test results, and other information for steps in the pipeline.

Unified Dashboard view of JFrog Pipelines

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/rzu5gsh0otk85noluxtf.png)

You can see each pipe and what is the status of its runs:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/bevlmijqvr16g3o5rf6y.png)

And for each task:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/kz0rie21diiqx60i8jt3.png)

And even you can see the yml file that is used in each step:

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/bu7kbf3rz7iq28v57hnc.png)

Some of the important functionality of [Steps](https://www.jfrog.com/confluence/display/JFROG/Pipelines+Steps)

#Generic Steps

A generic step is for general-purpose execution. The Bash and PowerShell steps, which execute any series of shell commands you specify, are the single generic steps for Linux and Windows runtimes, respectively.

#Native Steps

Pipelines native steps, you only have to tell your automation server what to do, not how to do it. As part of the JFrog Platform, Pipelines natively knows the best way to publish your builds to Artifactory, as well as build and deliver release packages through Distribution. Native steps provide you quick building blocks to perform the everyday tasks that fill your Artifactory repositories.

[Start your free trial on JFrog Platform](https://jfrog.com/artifactory/free-trial/?int_source=Blog%20Post)


Hope this helps! :)