Configure a pipeline in the UI
Create a pipeline from a template in Oore when the repository has no workflow file.
Create a pipeline in the Oore web UI when the repository has no Oore workflow file. The settings stay in Oore. Oore does not add or change any file in the repository.
What you need
- A project linked to a repository. See Create a project.
- Project developer, maintainer, instance admin, or instance owner access.
1. Open pipeline setup
Open the project’s Pipelines tab. Select Set up a build for the first pipeline, or Add pipeline when the project already has one.
If Oore finds a valid .oore.yaml or .oore.yml on the default branch, it
offers that workflow instead. Select Set up manually only when the
pipeline should ignore the repository file.
2. Pick a template
Under Start from, select the closest template:
| Template | What it sets up |
|---|---|
| Android test app | A debug APK with flutter build apk --debug. No signing needed |
| Release Android | A release Android build with release signing turned on |
| iOS + Android | Both mobile platforms. Add signing before you run it |
| All platforms | Android, iOS, and macOS |
| Custom | Android only, with no template commands. Change anything you need |
3. Review the settings
Every setting has a default that builds a standard Flutter app. Change only what your app needs:
- Basics for the pipeline name, platforms, Flutter version, and build number offset.
- Build for commands before and after the platform build, per-platform arguments and overrides, environment variables, artifact patterns, and the runner.
- Signing for Android keystores and iOS certificates or API keys.
- Triggers for source events, branch and path filters, schedules, limits, and approvals.
What will run shows the exact steps the runner will run with these settings.
A project that points at a repository on the Oore Mac has no source to send push or pull request events. Its builds start from the UI, the API, or a schedule.
4. Create the pipeline
Select Create pipeline.
Check the result
Oore shows Pipeline created and opens Run build with the new pipeline
selected. Run a build and check that it ends as Succeeded with the
artifacts you expect.
Troubleshooting
Oore uses the repository file instead of these settings
A pipeline whose Config source is Use repo config if found (.oore.yaml, .oore.yml) uses the file whenever it exists at the commit being built. Remove the file, or have this pipeline read a different path with Choose a config file.
Oore reports that the repository workflow is invalid
Fix the file. Oore never falls back to the UI settings when the selected file exists but is invalid.
Trigger events are unavailable
Pipelines for a repository on the Oore Mac start from the UI, the API, or a schedule. Connect GitHub or GitLab to build on pushes and pull requests.
Next step
Trigger a build. When the pipeline works, consider
moving it into .oore.yaml.