vriska/hydra
0
0
Fork 0
forked from lix-project/hydra
Code Pull requests Activity

Merge pull request #1054 from rybak/docs-typos

Browse source 
docs: fix typos
This commit is contained in:
Eelco Dolstra 2021-11-02 15:28:36 +01:00 committed by GitHub
parent 9ae676072c a462a9f488
commit 492476bbfe
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -31,13 +31,13 @@ $ hydra-create-user <USER> --full-name '<NAME>' \
--email-address '<EMAIL>' --password <PASSWORD> --role admin --email-address '<EMAIL>' --password <PASSWORD> --role admin
``` ```
Afterwards you should be able to log by clicking on "_Sign In_" on the top right of the web interface using the credentials specified by `hydra-crate-user`. Once you are logged in you can click "_Admin -> Create Project_" to configure your first project. Afterwards you should be able to log by clicking on "_Sign In_" on the top right of the web interface using the credentials specified by `hydra-create-user`. Once you are logged in you can click "_Admin -> Create Project_" to configure your first project.
### Creating A Simple Project And Jobset ### Creating A Simple Project And Jobset
In order to evaluate and build anything you need to crate _projects_ that contain _jobsets_. Hydra supports imperative and declarative projects and many different configurations. The steps below will guide you through the required steps to creating a minimal imperative project configuration. In order to evaluate and build anything you need to create _projects_ that contain _jobsets_. Hydra supports imperative and declarative projects and many different configurations. The steps below will guide you through the required steps to creating a minimal imperative project configuration.
#### Creating A Project #### Creating A Project
Log in as adminstrator, click "_Admin_" and select "_Create project_". Fill the form as follows: Log in as administrator, click "_Admin_" and select "_Create project_". Fill the form as follows:
- **Identifier**: `hello` - **Identifier**: `hello`
- **Display name**: `hello` - **Display name**: `hello`
@ -53,7 +53,7 @@ After creating a project you are forwarded to the project page. Click "_Actions_
- **Check interval**: 60 - **Check interval**: 60
- **Scheduling shares**: 1 - **Scheduling shares**: 1
We have to add two inputs for this jobset. One for _nixpkgs_ and one for _hydra_ (which we are referrencing in the Nix expression above): We have to add two inputs for this jobset. One for _nixpkgs_ and one for _hydra_ (which we are referencing in the Nix expression above):
- **Input name**: `nixpkgs` - **Input name**: `nixpkgs`
- **Type**: `Git checkout` - **Type**: `Git checkout`

2
doc/manual/src/hacking.md
View file

@ -74,7 +74,7 @@ $ nix-build release.nix -A build.x86_64-linux
### Connecting to the database ### Connecting to the database
Assuming you're running the the default configuration with `foreman start`, Assuming you're running the default configuration with `foreman start`,
open an interactive session with Postgres via: open an interactive session with Postgres via:
```console ```console

2
doc/manual/src/notifications.md
View file

@ -11,7 +11,7 @@ Note that the notification format is subject to change and should not be conside
### `build_started` ### `build_started`
* **Payload:** Exactly one value, the ID of the build. * **Payload:** Exactly one value, the ID of the build.
* **When:** Issued directly before building happens, and only if the derivation's outputs cannot be subsituted. * **When:** Issued directly before building happens, and only if the derivation's outputs cannot be substituted.
* **Delivery Semantics:** Ephemeral. `hydra-notify` must be running to react to this event. No record of this event is stored. * **Delivery Semantics:** Ephemeral. `hydra-notify` must be running to react to this event. No record of this event is stored.
### `step_finished` ### `step_finished`