Robert Hensing
|
519a435b08
|
nixos/hercules-ci-agent: Set default labels
|
2021-05-04 16:29:05 +02:00 |
|
Robert Hensing
|
4abd56732e
|
nixos/hercules-ci-agent: Set default concurrency to auto
|
2021-05-04 16:28:31 +02:00 |
|
Robert Hensing
|
696294ea9f
|
Improve todo
|
2021-02-10 10:36:00 +01:00 |
|
Robert Hensing
|
460ba46a4a
|
nixos/hercules-ci-agent: Add myself to meta.maintainers
|
2021-02-10 09:50:27 +01:00 |
|
Robert Hensing
|
0c22957751
|
nixos/hercules-ci-agent: Improve concurrentTasks option doc
|
2021-02-10 09:49:57 +01:00 |
|
Robert Hensing
|
fbabab7b16
|
nixos/hercules-ci-agent: Format with nixpkgs-fmt
|
2021-02-10 09:49:21 +01:00 |
|
Robert Hensing
|
c808983caa
|
nixos/hercules-ci-agent: Remove patchNix
|
2021-02-06 15:35:42 +01:00 |
|
lf-
|
b37bbca521
|
nixos/modules: fix systemd start rate-limits
These were broken since 2016:
https://github.com/systemd/systemd/commit/f0367da7d1a61ad698a55d17b5c28ddce0dc265a
since StartLimitIntervalSec got moved into [Unit] from [Service].
StartLimitBurst has also been moved accordingly, so let's fix that one
too.
NixOS systems have been producing logs such as:
/nix/store/wf98r55aszi1bkmln1lvdbp7znsfr70i-unit-caddy.service/caddy.service:31:
Unknown key name 'StartLimitIntervalSec' in section 'Service', ignoring.
I have also removed some unnecessary duplication in units disabling
rate limiting since setting either interval or burst to zero disables it
(https://github.com/systemd/systemd/blob/ad16158c10dfc3258831a9ff2f1a988214f51653/src/basic/ratelimit.c#L16)
|
2020-10-31 01:35:56 -07:00 |
|
Robert Hensing
|
346a1b0ec6
|
nixos/hercules-ci-agent: init
|
2020-08-23 20:13:15 +02:00 |
|