Configure pipelines

A pipeline tells Oore what to build for a project, with which credentials and under which rules. What it builds can come from settings saved in Oore or from a .oore.yaml file in the repository. Credentials, approvals and per-workflow overrides always stay in Oore. Read Files, pipelines and workflows for which part lives where.

Set up a pipeline

• Configure a pipeline in the UI from a template, without a file.
• Move a pipeline into .oore.yaml so it changes with the code.
• Add pipelines from the repository: let Oore turn the config files it finds into pipelines, and check each pipeline’s health.

Work with workflows

• Run two workflows from one file, such as an ad hoc build for testers and a store release, each with its own signing and publishing.
• Move credentials into the project library so each workflow signs with its own keys.

Inputs and rules

• Use secrets in a pipeline for tokens and keys.
• Set triggers, timeouts, and approvals.

Reference

• .oore.yaml version 2
• Pipeline settings, including the default workflow, per-workflow settings and health

Next step

New to pipelines? Configure a pipeline in the UI first, then move it into .oore.yaml when it works.