Hydra: Difference between revisions

Line 38:

This subsection provides an overview of the Hydra-specific definitions and how to configure them.

* 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.

* Project:

* Job Set:

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

* Release Set: ~~TODO~~

* Job Set:

* Build ~~Job: TODO~~

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

* Build ~~Recipes~~:~~TODO~~

* Job:

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

* Release Set:

Defines all the jobs which are described in your release. By convention a file called<code>release.nix</code> is being used. See the [https://nixos.org/hydra/manual/#idm140737315920320 Hydra manual for Build Recipes] for a thorough description of the structure.

* Build:

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

== Resources ==

@@ Line 38: / Line 38: @@
 This subsection provides an overview of the Hydra-specific definitions and how to configure them.
-* 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.
+* Project:
-* Job Set:
+  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
-* Release Set: TODO
+* Job Set:
-* Build Job: TODO
+  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
-* Build Recipes:TODO
+* Job:
+  A closure which will be built as part of a jobset (like a single package, iso image or tarball)
+* Release Set:
+  Defines all the jobs which are described in your release. By convention a file called<code>release.nix</code> is being used. See the [https://nixos.org/hydra/manual/#idm140737315920320 Hydra manual for Build Recipes] for a thorough description of the structure.
+* Build:
+  Instantiation of a Job which is being triggered by being part of the release set
 == Resources ==