Projects, Jobs, and Runners#
Check the project, runner, region, uploaded files, and expected output before starting a job.
Overview#
A project groups related work. A job is one requested operation, and a runner is the machine or managed service that executes it. The Cloud Console shows which runners and job actions are available to the signed-in account.
Execution Choices#
Runner category |
Execution location |
Use only when |
|---|---|---|
Local |
Current customer machine |
The product reports the required local capability and toolchain as available |
Customer-managed |
Infrastructure controlled by the customer’s organization |
The account and project show that runner as available |
Altifigence-managed |
Altifigence-managed capacity |
The operation, cost or credit information, and submit action are shown for the account |
Local tools can run without a managed runner. Customer-managed and Altifigence-managed runners appear only when they are enabled for the project.
Before Starting a Job#
Confirm all of the following in the product or console:
organization and project;
operation and capability state;
selected runner and region when applicable;
exact source or artifact bundle that will leave the machine;
toolchain, target, constraints, and execution limits;
expected usage or credit charge;
output, retention, and cancellation behavior.
Do not submit restricted project data if the destination, region, or uploaded files are unclear.
Job Records#
A useful job record identifies its project, action, runner, source revision or digest, configuration, timestamps, state, logs, and artifacts. Keep it with the project so the result can be reproduced later.
CLI Boundary#
The current public CLI archive includes remote command shapes, but it does not provide interactive login, token issuance, source upload, or a complete Cloud job flow. Use the Cloud Console for actions shown there; do not treat an HTTP route or 401 response as an available CLI workflow.