Follow a build: status, graph and logs¶
Open a build from its list. The page updates itself while the build runs: no reload.
Status¶
The status goes Planning, then Building, then Succeeded or Failed, with a message such as “Building 38/86 tasks done, 3 running”.
The planner’s log¶
While it is planning, follow the planner’s log live opens the log as it is written. If planning fails, the end of the log is shown on the page with the reason (a package the tree does not have, a setting that cannot be met).
The plan¶
Which packages are needed, and how many jobs that makes. In the summary, already in the bin repo is what is reused or taken ready-made instead of compiled.
The graph¶
The graph shows how the build runs.
Each box is a job: one or more packages built together.
An arrow means this must finish first.
The coloured bands, top to bottom, are steps: everything in one band can run at the same time, as many as the infrastructure allows, and a band starts when the ones above it are done.
Colours: white is waiting, amber is running, green is done, red failed.
The blue fetch band at the top holds the copy jobs: ready-made packages being pulled into your repository (see Take ready-made packages (pull from)). Nothing waits for them. The packages below it are what really compiles.
Under the picture, as text gives the same plan as a list.
The jobs and their logs¶
A table with one row per job: its packages, what it waits for, and a log.
While a job runs, its live link opens its log as it is written: the compiler’s own output, so you can watch
gccornginxbuild.When a job has finished, its log is kept beside your packages in the repository. If something failed, that log says why.
A job that installs packages from a ready-made source lists their logs too. A copy job lists the logs of the packages it brings over.
job output is what the job itself printed, saved for jobs that succeeded as well as for failed ones.
Note
Logs are kept in your binary repository. If a row says not kept, the repository has no upload proxy and keeps no logs.
Scan now, and security¶
When a build has succeeded, it is checked against security advisories; see Security: vulnerabilities in what you build.
Mail, pause and delete¶
Mail me when this finishes — once, whichever way it ends.
Plan only (in the form) pauses a build.
Delete removes the build. Packages already in your repository stay there.