Oore CI

How Oore chooses pipeline configuration

Understand repository-workflow precedence, the UI alternative, and the pinned-checkout boundary.

Oore reads a checked-in workflow before the UI configuration. This keeps the build definition with the commit.

The selection model

For each build, the Direct macOS runner reads configuration from the pinned repository checkout:

  1. Oore checks the pipeline’s config path. A pipeline with .oore.yaml also checks the legacy .oore.yml when .oore.yaml does not exist.
  2. Oore uses the pipeline configuration saved in the UI only when the selected repository file does not exist.

The selected file wins when it exists. If it is invalid, the build fails instead of silently using different UI settings.

Why the file wins

A repository workflow is reviewed and versioned with the code it builds. A build pinned to an older commit reads the workflow from that same checkout, so a later edit does not rewrite the older build’s instructions.

The UI path stays useful for a first build and for teams that do not want a repository workflow yet. It is an alternative source when the selected file is absent, not a recovery path for an invalid file.

Flutter version is a separate choice

A checked-in .fvmrc overrides the Flutter version saved in repository YAML or the UI. This lets a repository keep its Flutter toolchain choice beside the application. Oore only reads the version from it; FVM itself is not used. In a VM build the version selects the image.

Effects

  • Changing UI commands does not override an existing selected repository file.
  • A typo or unknown field in that file fails visibly.
  • Validating the file before pushing prevents a configuration failure on the runner.
  • You can start with the Android test app template in the UI and move to .oore.yaml after the first successful build.

What the file can and cannot decide

The file decides what a build runs. It names signing identities and store destinations, but the credentials, gates and per-workflow overrides stay in Oore. See Files, pipelines and workflows for the split and the order in which each is resolved.

The repository can add pipelines

Oore also reads the config files on the default branch ahead of any build, to offer each unused file as a pipeline and to show each pipeline’s health. See Add pipelines from the repository.

Next step

Move a pipeline into .oore.yaml, then use the oore pipeline validate reference for exact command behavior and the .oore.yaml reference for accepted fields.