Hydra: Difference between revisions

Dander (talk | contribs)
m wiki content team decided that given this page is one of the first pages nix* users read, it should be clear that this is for Nix(OS) package developers
Pigs (talk | contribs)
m link to postgres and flakes
(One intermediate revision by one other user not shown)
Line 2: Line 2:
<translate>
<translate>
<!--T:1-->
<!--T:1-->
{{note| Hydra is for Nix/NixOS package developers, it is not needed to use NixOS.}}
{{note| Hydra is intended to be used by Nix/NixOS package developers; it is not needed to simply use NixOS.}}


Hydra is a tool for continuous integration testing and software release that uses a purely functional language to describe build jobs and their dependencies. Continuous integration is a simple technique to improve the quality of the software development process. An automated system continuously or periodically checks out the source code of a project, builds it, runs tests, and produces reports for the developers. Thus, various errors that might accidentally be committed into the code base are automatically caught.
Hydra is a tool for continuous integration testing and software release that uses a purely functional language to describe build jobs and their dependencies. Continuous integration is a simple technique to improve the quality of the software development process. An automated system continuously or periodically checks out the source code of a project, builds it, runs tests, and produces reports for the developers. Thus, various errors that might accidentally be committed into the code base are automatically caught.
Line 32: Line 32:


<!--T:36-->
<!--T:36-->
The module will automatically enable postgresql if you do not change the <code>services.hydra.dbi</code> option. Database layout will be created automatically by the Hydra service, however keep in mind that some state will be stored in the database and a complete stateless configuration is currently not possible - do your backups.
The module will automatically enable [[PostgreSQL|postgresql]] if you do not change the <code>services.hydra.dbi</code> option. Database layout will be created automatically by the Hydra service, however keep in mind that some state will be stored in the database and a complete stateless configuration is currently not possible - do your backups.


<!--T:37-->
<!--T:37-->
Line 79: Line 79:


<!--T:10-->
<!--T:10-->
* Type: Flake
* Type: [[Flakes|Flake]]


<!--T:40-->
<!--T:40-->