... | ... | @@ -6,6 +6,10 @@ The information about the nightly builds is aggregated thus: |
|
|
- [ Information on the status of the nightly builds](http://haskell.inf.elte.hu/builders/). This is basically a large table with hyperlinks to the individual builds in it.
|
|
|
- [ Fully-built documentation for the nightly builds](http://haskell.inf.elte.hu/docs/). Here, for example, is the [ user manual and library Haddocks for HEAD](http://haskell.inf.elte.hu/docs/latest/html/).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Conventions
|
|
|
|
|
|
|
... | ... | @@ -14,9 +18,15 @@ Currently, the table follows the following conventions below. |
|
|
## Names
|
|
|
|
|
|
|
|
|
|
|
|
Every [builder](builder) has a distinct name, similar to an identifier, this is the username of the client configured to execute the build commands. These names are generated by the following scheme:
|
|
|
|
|
|
|
|
|
>
|
|
|
>
|
|
|
> `[validator$n-]$operating_system-$architecture-$branch`.
|
|
|
>
|
|
|
>
|
|
|
|
|
|
|
|
|
For example: `validator1-linux-x86-head`, `freebsd-amd64-stable`.
|
... | ... | @@ -54,29 +64,52 @@ Each build has a result, which is both marked by a distinct color and a brief na |
|
|
# Build Pages
|
|
|
|
|
|
|
|
|
|
|
|
The builder summary pages store information on every build, however, from the main page, **only the top 10 builds are shown** for each of the builders. In order to see the older builds, they can be individually accessed at the builder's sub-page. It has the URL of the following format, but they can be also accessed from the main page:
|
|
|
|
|
|
|
|
|
>
|
|
|
>
|
|
|
> [ http://haskell.inf.elte.hu/builders/$builder/](http://haskell.inf.elte.hu/builders/$builder/)
|
|
|
>
|
|
|
>
|
|
|
|
|
|
|
|
|
where `$builder` is the name of the builder by the conventions described above. This page contains the directory of all builds were ever collected for the builder in question.
|
|
|
|
|
|
|
|
|
|
|
|
Note that the entries on this page are in the following format:
|
|
|
|
|
|
|
|
|
>
|
|
|
>
|
|
|
> `$n: $result, $date $time UTC`
|
|
|
>
|
|
|
>
|
|
|
|
|
|
|
|
|
where `$n` is the serial number of the build, `$result` is the result of the build (see above for explanation), `$date` and `$time` is date and time when the build was done. Following those links will lead to the build pages:
|
|
|
|
|
|
|
|
|
>
|
|
|
>
|
|
|
> [ http://haskell.inf.elte.hu/builders/$builder/$n.html](http://haskell.inf.elte.hu/builders/$builder/$n.html)
|
|
|
>
|
|
|
>
|
|
|
|
|
|
### Header
|
|
|
|
|
|
|
|
|
|
|
|
On those build pages, one can see the scheduled steps and their results. Such pages start with a header, which is of the following format:
|
|
|
|
|
|
|
|
|
>
|
|
|
>
|
|
|
> `$builder ($info), build $n, $result`
|
|
|
>
|
|
|
>
|
|
|
|
|
|
|
|
|
where `$builder` is the name of the builder (per the previously introduced conventions), `$info` is the longer description of the builder, often containing the name of the maintainer, `$n` is the serial number of the build, and `$result` is the overall result of the build.
|
... | ... | @@ -128,9 +161,15 @@ Some of the steps are configured to inline their outputs in the build page to sh |
|
|
## Step Pages
|
|
|
|
|
|
|
|
|
|
|
|
Note that each of the steps are hyperlinked, which means they have links to contain further information on the details. Such sub-pages can be also individually accessed as:
|
|
|
|
|
|
|
|
|
>
|
|
|
>
|
|
|
> [ http://haskell.inf.elte.hu/builders/$builder/$build/$step.html](http://haskell.inf.elte.hu/builders/$builder/$build/$step.html)
|
|
|
>
|
|
|
>
|
|
|
|
|
|
|
|
|
Step pages have the following structure:
|
... | ... | |