gchristensen changed the topic of #nixos-borg to: https://www.patreon.com/ofborg https://monitoring.nix.ci/dashboard/db/ofborg?refresh=10s&orgId=1&from=now-1h&to=now "I get to skip reviewing the PHP code and just wait until it is rewritten in something sane, like POSIX shell. || https://logs.nix.samueldr.com/nixos-borg
orivej has quit [Ping timeout: 276 seconds]
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-borg
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #nixos-borg
supersandro2000 has quit [Quit: The Lounge - https://thelounge.chat]
supersandro2000 has joined #nixos-borg
cole-h has joined #nixos-borg
evanjs has quit [Ping timeout: 276 seconds]
cole-h has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-borg
orivej_ has joined #nixos-borg
orivej has quit [Ping timeout: 276 seconds]
cole-h has joined #nixos-borg
cole-h has quit [Ping timeout: 256 seconds]
cole-h has joined #nixos-borg
<gchristensen> oh btw cole-h I found a bug in the ofborg deployment scripts!
<cole-h> :O
<gchristensen> I know :o
<gchristensen> if Server Intake intakes new servers, it should commit and push and then *exit*
<gchristensen> because the deploy phase will use the old servers!
<gchristensen> this will then trigger a new pipeline run, which will then have a noop intake step
<cole-h> gchristensen: oooh, there's an automatic retry attribute
<gchristensen> well won't it trigger a deploy by virtue of the push happening?
<cole-h> is that how it works?
<cole-h> :D
<gchristensen> I think so? hmm :P
* cole-h doesn't see how a push would make it redeploy
<cole-h> Could be missing something though
<gchristensen> when a push happens does buildkite start a job automatically?
<cole-h> I don't think so?
<gchristensen> oh