Configure a pipeline in the UI
Create a pipeline in Oore when the repository does not own a workflow file.
Configure a pipeline in the UI when the repository does not contain a selected Oore workflow. UI configuration remains in Oore; it does not add or change a file in the repository.
What you need
- A project linked to a repository.
- Project developer, maintainer, instance admin, or instance owner access.
- The commands and artifact patterns needed to build the application.
1. Open pipeline setup
Open the project, select Pipelines, then select Set up a build.
If Oore finds a valid repository workflow, it recommends that workflow. Select Set up manually instead only when you intend to configure the UI path.
2. Choose a starting point
Under Choose a starting point, select the closest starter:
- Quick Debug APK for the shortest Android build, with no uploaded release-signing material required.
- Release Android for a release Android pipeline.
- iOS + Android or All Platforms for a wider mobile build.
- Custom to start without template commands.
3. Review the configuration
Set the Pipeline name and Build for platforms values. Expand the remaining sections only when you need to change them:
- Configuration for config selection, Flutter version, and commands.
- Environment Variables for application build values.
- Artifacts for one pattern per line.
- Triggers for source events, branch patterns, cancellation, and concurrency.
For a local Git repository, the UI correctly limits the pipeline to manual UI or API triggers because there is no source webhook.
4. Create the pipeline
Select Create.
Verify the result
Oore shows Pipeline created and lists the pipeline on the project. Open it and confirm the expected platforms, commands, artifact patterns, and trigger settings.
Troubleshooting
A repository workflow takes precedence
For an automatic config path, Oore checks .oore.yaml and then .oore.yml.
If a selected file exists, it owns the build. Remove or intentionally change
that repository selection if the UI should own the pipeline.
A repository workflow is invalid
Repair the selected file. Oore does not fall back to a different UI definition when the selected file exists but is invalid.
Webhook triggers are unavailable
Local Git pipelines are manual only. Connect GitHub or GitLab through Sources before configuring source-event triggers.
Next step
Trigger a build and verify the pipeline on one pinned revision.