Hydra: Difference between revisions

Line 52:

This option leads to the file /etc/nix/machines being created. If the hydra service config is still set to buildMachinesFiles = [], then it will be ignored, so remove this option again or add /etc/nix/machines to it.

This option leads to the file /etc/nix/machines being created. If the hydra service config is still set to buildMachinesFiles = [], then it will be ignored, so remove this option again or add <code>/etc/nix/machines</code> to it.

Line 58:

Configure jobset the following:

Configure jobset to the following:

Line 144:

==== Project ====

A cluster of Jobs which are all coming from a single input (like a git checkout), the first thing you will need to create. Every Job should be able to be built independently from another. Most of the time the project maps to a single repository like <code>nixpkgs</code>. It is comparable to the project definition in Jenkins

A cluster of Jobs which are all coming from a single input (like a git checkout), the first thing you will need to create. Every Job should be able to be built independently from another. Most of the time the project maps to a single repository like <code>nixpkgs</code>. It is comparable to the project definition in Jenkins.

==== ~~Job Set~~ ====

==== Jobsets ====

A list of jobs which will be run. Often a ~~Jobset~~ fits to a certain branch (master, staging, stable). A ~~jobset~~ is defined by its inputs and will trigger if these inputs change~~, e~~.~~g. like~~ a new commit onto a branch is added. ~~Job sets~~ may depend on each other

A Jobset is a list of jobs which will be run. Often a jobset fits to a certain branch (master, staging, stable). A Jobset is defined by its inputs and will trigger if these inputs change. For example when a new commit onto a branch is added. Jobsets may depend on each other.

==== Job ====

A closure which will be built as part of a ~~jobset~~ (like a single package, iso image or tarball)

A closure which will be built as part of a job set (like a single package, iso image or tarball).

Line 160:

==== Evaluation ====

The process of interpreting nix code into a list of <code>.drv files</code>. These files are the build recipes for all related outputs. You can introspect these files by running <code>nix show-derivation nixpkgs.hello</code>

The process of interpreting nix code into a list of <code>.drv files</code>. These files are the build recipes for all related outputs. You can introspect these files by running <code>nix show-derivation nixpkgs.hello</code>.

==== Build ====

Instantiation of a Job which is being triggered by being part of the release set

Instantiation of a Job which is being triggered by being part of the release set.

@@ Line 52: / Line 52: @@
 <!--T:7-->
-This option leads to the file /etc/nix/machines being created. If the hydra service config is still set to buildMachinesFiles = [], then it will be ignored, so remove this option again or add /etc/nix/machines to it.
+This option leads to the file /etc/nix/machines being created. If the hydra service config is still set to buildMachinesFiles = [], then it will be ignored, so remove this option again or add <code>/etc/nix/machines</code> to it.
@@ Line 58: / Line 58: @@
 <!--T:9-->
-Configure jobset the following:
+Configure jobset to the following:
 <!--T:10-->
@@ Line 144: / Line 144: @@
 <!--T:23-->
 ==== Project ====
-A cluster of Jobs which are all coming from a single input (like a git checkout), the first thing you will need to create. Every Job should be able to be built independently from another. Most of the time the project maps to a single repository like <code>nixpkgs</code>. It is comparable to the project definition in Jenkins
+A cluster of Jobs which are all coming from a single input (like a git checkout), the first thing you will need to create. Every Job should be able to be built independently from another. Most of the time the project maps to a single repository like <code>nixpkgs</code>. It is comparable to the project definition in Jenkins.
 <!--T:24-->
-==== Job Set ====
+==== Jobsets ====
-A list of jobs which will be run. Often a Jobset fits to a certain branch (master, staging, stable). A jobset is defined by its inputs and will trigger if these inputs change, e.g. like a new commit onto a branch is added. Job sets may depend on each other
+A Jobset is a list of jobs which will be run. Often a jobset fits to a certain branch (master, staging, stable). A Jobset is defined by its inputs and will trigger if these inputs change. For example when a new commit onto a branch is added. Jobsets may depend on each other.
 <!--T:25-->
 ==== Job ====
-A closure which will be built as part of a jobset (like a single package, iso image or tarball)
+A closure which will be built as part of a job set (like a single package, iso image or tarball).
 <!--T:26-->
@@ Line 160: / Line 160: @@
 <!--T:27-->
 ==== Evaluation ====
-The process of interpreting nix code into a list of <code>.drv files</code>. These files are the build recipes for all related outputs. You can introspect these files by running <code>nix show-derivation nixpkgs.hello</code>
+The process of interpreting nix code into a list of <code>.drv files</code>. These files are the build recipes for all related outputs. You can introspect these files by running <code>nix show-derivation nixpkgs.hello</code>.
 <!--T:28-->
 ==== Build ====
-Instantiation of a Job which is being triggered by being part of the release set
+Instantiation of a Job which is being triggered by being part of the release set.
 <!--T:29-->