spov

New job

An agent works in a sandbox until it says it is done. Then spov judges what it left behind, with your check if you give one.

The agent sees this for the whole run. Say what done looks like.

Result
Repositories

Loading…

Each one is cloned into /workspace. The agent starts there, not inside a repository.

When it runs out, spov stops the job, keeps what it made and judges it.

How the time limit counts

Time you spend steering the job does not count, and resuming it continues with what is left. The default is set in Settings.

Which repositories the job's git credentials are used on.

What every repository allows

The agent can push to and open pull requests on repositories you did not choose here. Where the credential is the deployment's rather than your own, it is allowed only if an admin has turned it on, and a job that asks for it is refused otherwise.

Run when the work ends, so the verdict has an exit status.

How the check is run

It runs in the sandbox at /workspace, so name the repository: ./<repo>/scripts/check.sh. Without it the verdict has only the agent's account of one. A command that cannot be run stops the job succeeding, so leaving this empty is better than guessing at it.

A job needs a goal; choose at least one repository.