Trigger a build
Queue one pipeline build from the Oore UI and verify the pinned revision.
Trigger a pipeline manually and confirm the exact repository revision Oore queued. This task does not change the pipeline or its source.
How a build moves from queue to artifact explains what happens after the build is queued.
What you need
- A linked app with at least one pipeline.
- App developer, maintainer, instance admin, or instance owner access.
- An online Direct macOS runner that is accepting new work.
1. Open the build dialog
Open the app and select Run build.
2. Choose what to build
- Select the Pipeline.
- Select the platforms for this run when the pipeline supports more than one.
- Enter the Branch to build.
- Add Commit SHA (optional) only when you need one exact revision.
- When the build uploads to a store, check Ready to submit?. The build sends the release notes of its app version; see Release notes and changes.
When both branch and commit SHA are present, the commit SHA wins. Without a commit SHA, Oore resolves the branch before it creates the queued build.
3. Run the build
Select Run build in the dialog. Oore opens the build after it has been queued.
Verify the result
The build detail shows its branch, pinned commit, pipeline, and selected
platforms. Follow the state and logs until the build reaches succeeded or
another terminal result.
Follow the build
The build page opens on Logs while the build runs, with a bar and a line such as “Step 3 of 6 · Build · about 4 min left” once the pipeline has a few successful runs to compare with. A build no runner has started lists the runners that can take it and why each has not yet. A finished build opens on Summary: the apps it made with Install, the stores it was sent to, what changed, its checks, its version, commit and author, and its activity, including tester feedback. A failed build opens on Logs, or on Tests when tests failed.
To run a build again with a different branch, workflow or notes, open the menu beside Re-run and choose Re-run with changes.
A build canceled because a newer push to the same branch started another one says Replaced by and links to that build.
Troubleshooting
The build waits because the Direct macOS runner is paused
An instance owner or admin can open Settings > Runners and turn on Accept builds from approved repositories. This resumes new claims; it does not create a second repository approval step.
The build reports that the source is unavailable
Ask an owner or admin to repair or relink the app source, then trigger a new build. A re-run does not move an older build snapshot to a different repository identity.
Oore asks for a branch or commit
Enter a branch, provide a commit SHA, or set the app’s default branch.
Connected GitHub and GitLab sources can also trigger enabled pipelines from verified webhook revisions. The HTTP contract is available in Create a build.
Next step
If the build must stop before completion, cancel the build.