A successful run of the pipeline in this Quickstart looks like this:
At least one node pool. This is the set of nodes that all pipeline steps will execute in. For more information, see Managing Pipelines Node Pools.
If you have a Cloud account, a node pool will already be available as part of your subscription.
pipelines.yml, which contains the declarations for all the resources and steps required to run the pipeline. This configuration is written in template format, so you will not need to change anything in this file.
Since your pipelines.yml config file is templatized, as shown in the table below, update the values.yml in your forked repository:
|Provide the name of the Github integration you added in Step 4.|
|Provide the path to your fork of this repository.|
| ||Provide the name of the Artifactory integration you added in the previous Step 4.|| |
| ||Provide the name of the local Maven repository in Artifactory you created in Step 3.|| |
And that's it. Your configuration is ready to go!
All pipeline definitions are global across JFrog Pipelines within a Project. The names of your pipelines and resources need to be unique within the Project in JFrog Pipelines.
demo_mavenis the names of your pipeline.
You can trigger the pipeline by committing a change to your repository, or by manually triggering it through the UI. Multiple steps can execute in parallel if the node pool has multiple build nodes available.
Let us now take a look at the pipeline definition files and what each section means.
The pipelines.yml file contains the templatized definition of your pipeline. This consists of the following: