... | ... | @@ -24,7 +24,7 @@ Every builder has a distinct name, similar to an identifier, this is the usernam |
|
|
For example: `validator1-linux-x86-head`, `freebsd-amd64-stable`.
|
|
|
|
|
|
|
|
|
If the builder's name is prefixed with `validator$n` then it does not upload files, it produces logs only by building GHC and running the `validate` command on it, hence the name. Its purpose is just to check if everything works okay on the given configuration. It is mostly used on platforms (such as Linux) where official nightly builds are offered in many other fashions, so the builder infrastructure does not attempt to reproduce this functionality. However, it was judged that is still useful to test the build on various non-standard configurations. Notice the `$n` at the end: this is just an every-increasing natural number to make the names unique.
|
|
|
If the builder's name is prefixed with `validator$n` then it does not upload files, it produces logs only by building GHC and running the `validate` command on it, hence the name. Its purpose is just to check if everything works okay on the given configuration. It is mostly used on platforms (such as Linux) where official nightly builds are offered in many other fashions, so the builder infrastructure does not attempt to reproduce this functionality. However, it was judged that is still useful to test the build on various non-standard configurations. Notice the `$n` at the end: this is just an ever-increasing natural number to make the names unique.
|
|
|
|
|
|
|
|
|
If the builder's name does not have the "validator" prefix, the builder attempts to create a daily snapshot for the given platform, which may be accessed through the builder sub-page, see below. Its purpose is to check if GHC builds on the given platform (and architecture) and provide publicly-accessible development snapshots every time when the build succeeds.
|
... | ... | |