# Pipelines
Source: https://docs.infraista.com/en/developer-tools/pipelines



Pipelines runs the jobs described in `.infraista/pipeline.yml` in your repository on every push,
pull request, schedule or manual run. Each job gets a fresh, isolated container that's removed when
the job ends, and the result is reported back to the commit and pull request as a status check
named `infraista/<pipeline name>`.

<Shot name="developer-tools/pipelines/list" alt="The Pipelines page listing the web-app pipeline with its repository, last run and status" />

## How it fits together [#how-it-fits-together]

| Part                    | What it is                                                                    |
| ----------------------- | ----------------------------------------------------------------------------- |
| **Pipeline**            | One repository and one pipeline file. A repository can have several pipelines |
| **Stages and jobs**     | Stages run in order; the jobs in a stage run in parallel                      |
| **Steps**               | Shell commands (`run:`) or built-in actions (`uses: infraista/checkout@v1`)   |
| **Runners**             | Managed runners (billed per minute) or your own self-hosted machines (free)   |
| **Secrets & variables** | Values your jobs read, for the organization, the pipeline or one environment  |
| **Environments**        | Where you deploy (staging, production), with approvals and other rules        |
| **Deploy targets**      | Servers, registries and cloud accounts a pipeline can deploy to by name       |

## Where to go next [#where-to-go-next]

<SectionIndex />