Code and Builds

Quant can write the CI pipeline of a new project for your runner pool, and move the builds of a project that exists. You do not have to edit runs-on yourself.

Set a default for new projects

On Cloud → CI runners, choose Use for new projects on a connected pool. The pool shows Default for new projects.

New cloud apps and sites in that pool’s GitHub organisation then build on the pool. To go back, choose Use GitHub-hosted runners on the pool.

The first pool that you create from a create form becomes the default automatically.

Choose the runners when you create a cloud app

When you create a cloud app from a template or import one from GitHub, the form has a CI runners field when your GitHub organisation has a connected pool. It starts on your default.

• Choose a pool, and Quant writes the pool’s labels into the repository’s workflow. For an ARM64 app, Quant uses the pool’s arm64 runners, so the image builds without emulation.
• Choose GitHub-hosted runners to keep the template’s runners.

A new repository is made private when you choose a pool, because Quant runners take jobs from private repositories only. The import form refuses a pool for a public repository.

Set up Quant CI runners from the form

If your GitHub organisation has no pool yet, the CI runners field offers Set up Quant CI runners…:

1. Choose a size and the architectures.
2. Choose Create pool and connect GitHub.
3. GitHub asks you to install the Quant CI runners app. Choose All repositories, so new repositories build without a further step.
4. GitHub returns you to the form with what you typed. The form selects the new pool when it is ready, in a few minutes.

You need permission to manage CI runner pools in your Quant organisation, and to install apps on the GitHub organisation.

Static sites and Studio sites

The static site and Studio create forms have no runner field. They use your default pool only when the build can start without a further step: the repository is private, and the Quant CI runners app can see all repositories, or the imported repository. Otherwise they use GitHub-hosted runners.

Move the builds of an app that exists

An app’s Environments page has a Code and builds card. It shows the app’s GitHub repository and where its builds run.

To move the builds to a pool:

1. In Code and builds, choose the pool.
2. Choose Move builds to Quant CI.
3. Quant opens a pull request on the repository that changes runs-on in its workflows. Review it and merge it on GitHub.

Nothing changes until you merge the pull request. To go back, revert it.

The card appears for apps that were created from a template or imported from GitHub in the dashboard. Quant refuses the move, with the reason, when the repository is public, when the Quant CI runners app cannot see it, or when no workflow uses runners that Quant can change.

When the app can see selected repositories only

If you installed the Quant CI runners app with Only select repositories, a new repository is not in that list, and its jobs wait for a runner. The create form warns you when you choose a pool, and the deployment progress shows The build is waiting for access with the steps.

Choose Manage access on GitHub on the pool and add the repository. Quant then finds the jobs that are waiting and runs them.