mdebray/tvl-depot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
tvl-depot/ci/pipelines/post-receive.nix

57 lines
1.5 KiB
Nix
Raw Normal View History

Add build, lint Emacs steps to post-receive pipeline TL;DR: - Define runEmacsScript to emacs/default.nix for ci/pipelines/post-receive - Write script.el to call (load init.el) and catch any errors - Lint Elisp with gonewest818/elisp-lint Also nice how Buildkite supports :gnu: emojis!
2020-08-27 19:27:12 +02:00
{ briefcase, pkgs, ... }:
Define BuildKite pipelines in Nix After a handful of failed attempts to run lint-secrets.sh due to a missing `git-secrets` executable on my git server, I decided that now was a good time to use Nix to define my BuildKite pipelines. TL;DR: - Delete ci/scripts directory - Define ci/pipelines/{briefcase,socrates}.nix Outside of this repository: - I logged into my admin account at git.wpcarro.dev and changed my Gitea post-receive hook to trigger the briefcase pipeline - I logged into my BuildKite account, deleted my build-briefcase pipeline, created a new briefcase pipeline that called: ```shell nix-build -A ci.pipelines.briefcase -o briefcase.yaml buildkite-agent pipeline upload briefcase.yaml ``` One day I will audit all of my ad-hoc, non-mono-repo activity (like the steps I listed above) and attempt to fit everything herein... one step at a time, though!
2020-08-21 12:12:57 +02:00
let
Allow configurable BRIEFCASE env var for CI These were hard-coded as $HOME/BRIEFCASE, which won't work in CI, since CI runs as the user buildkite-agent-socrates, whose $HOME directory doesn't exist.
2020-08-31 02:16:31 +02:00
inherit (builtins) fetchGit path toJSON;
inherit (briefcase.emacs) initEl runScript;
elispLintSrc = fetchGit {
Add build, lint Emacs steps to post-receive pipeline TL;DR: - Define runEmacsScript to emacs/default.nix for ci/pipelines/post-receive - Write script.el to call (load init.el) and catch any errors - Lint Elisp with gonewest818/elisp-lint Also nice how Buildkite supports :gnu: emojis!
2020-08-27 19:27:12 +02:00
url = "https://github.com/gonewest818/elisp-lint";
rev = "2b645266be8010a6a49c6d0ebf6a3ad5bd290ff4";
};
Define BuildKite pipelines in Nix After a handful of failed attempts to run lint-secrets.sh due to a missing `git-secrets` executable on my git server, I decided that now was a good time to use Nix to define my BuildKite pipelines. TL;DR: - Delete ci/scripts directory - Define ci/pipelines/{briefcase,socrates}.nix Outside of this repository: - I logged into my admin account at git.wpcarro.dev and changed my Gitea post-receive hook to trigger the briefcase pipeline - I logged into my BuildKite account, deleted my build-briefcase pipeline, created a new briefcase pipeline that called: ```shell nix-build -A ci.pipelines.briefcase -o briefcase.yaml buildkite-agent pipeline upload briefcase.yaml ``` One day I will audit all of my ad-hoc, non-mono-repo activity (like the steps I listed above) and attempt to fit everything herein... one step at a time, though!
2020-08-21 12:12:57 +02:00
pipeline.steps = [
Abandon the pre-receive hook I wanted Gitea to call Buildkite's pre-receive pipeline and either accept or reject the incoming code depending on the outcome. The problem is that I can only *create* builds from Gitea's pre-receive hook. Now I'm left with two options: 1. run the lint-secrets step in post-receive 2. run `/nix/store/<hash>/git-secrets --scan-history $REPO_PATH` in Gitea As far as I can tell, I cannot define Gitea hooks in Nix, which is unfortunate; otherwise, option 2 would appeal more. I'm doing option one for now.
2020-08-22 10:09:15 +02:00
{
key = "lint-secrets";
command = "${pkgs.git-secrets}/bin/git-secrets --scan-history";
label = ":broom: lint secrets";
}
Define BuildKite pipelines in Nix After a handful of failed attempts to run lint-secrets.sh due to a missing `git-secrets` executable on my git server, I decided that now was a good time to use Nix to define my BuildKite pipelines. TL;DR: - Delete ci/scripts directory - Define ci/pipelines/{briefcase,socrates}.nix Outside of this repository: - I logged into my admin account at git.wpcarro.dev and changed my Gitea post-receive hook to trigger the briefcase pipeline - I logged into my BuildKite account, deleted my build-briefcase pipeline, created a new briefcase pipeline that called: ```shell nix-build -A ci.pipelines.briefcase -o briefcase.yaml buildkite-agent pipeline upload briefcase.yaml ``` One day I will audit all of my ad-hoc, non-mono-repo activity (like the steps I listed above) and attempt to fit everything herein... one step at a time, though!
2020-08-21 12:12:57 +02:00
{
Define Buildkite pipelines corresponding to git server hooks I think maintaining a 1:1 correspondence with the git server hook makes sense right now. Let's try it out!
2020-08-21 19:40:30 +02:00
key = "build-briefcase";
Surround subshell in 2x-quotes This wasn't a bug; it's just good practice.
2020-08-31 01:48:30 +02:00
command = ''
nix-build . -I briefcase="$(pwd)" --no-out-link --show-trace
'';
Define Buildkite pipelines corresponding to git server hooks I think maintaining a 1:1 correspondence with the git server hook makes sense right now. Let's try it out!
2020-08-21 19:40:30 +02:00
label = ":nix: build briefcase";
Abandon the pre-receive hook I wanted Gitea to call Buildkite's pre-receive pipeline and either accept or reject the incoming code depending on the outcome. The problem is that I can only *create* builds from Gitea's pre-receive hook. Now I'm left with two options: 1. run the lint-secrets step in post-receive 2. run `/nix/store/<hash>/git-secrets --scan-history $REPO_PATH` in Gitea As far as I can tell, I cannot define Gitea hooks in Nix, which is unfortunate; otherwise, option 2 would appeal more. I'm doing option one for now.
2020-08-22 10:09:15 +02:00
depends_on = "lint-secrets";
Define Buildkite pipelines corresponding to git server hooks I think maintaining a 1:1 correspondence with the git server hook makes sense right now. Let's try it out!
2020-08-21 19:40:30 +02:00
}
Add build, lint Emacs steps to post-receive pipeline TL;DR: - Define runEmacsScript to emacs/default.nix for ci/pipelines/post-receive - Write script.el to call (load init.el) and catch any errors - Lint Elisp with gonewest818/elisp-lint Also nice how Buildkite supports :gnu: emojis!
2020-08-27 19:27:12 +02:00
{
key = "init-emacs";
Allow configurable BRIEFCASE env var for CI These were hard-coded as $HOME/BRIEFCASE, which won't work in CI, since CI runs as the user buildkite-agent-socrates, whose $HOME directory doesn't exist.
2020-08-31 02:16:31 +02:00
command = let
scriptEl = path {
path = ./script.el;
name = "script.el";
};
runScriptEl = runScript {
script = scriptEl;
briefcasePath = "$(pwd)";
};
in "${runScriptEl} ${initEl}";
Add build, lint Emacs steps to post-receive pipeline TL;DR: - Define runEmacsScript to emacs/default.nix for ci/pipelines/post-receive - Write script.el to call (load init.el) and catch any errors - Lint Elisp with gonewest818/elisp-lint Also nice how Buildkite supports :gnu: emojis!
2020-08-27 19:27:12 +02:00
label = ":gnu: initialize Emacs";
depends_on = "build-briefcase";
}
Define Buildkite pipelines corresponding to git server hooks I think maintaining a 1:1 correspondence with the git server hook makes sense right now. Let's try it out!
2020-08-21 19:40:30 +02:00
{
key = "build-socrates";
Define BuildKite pipelines in Nix After a handful of failed attempts to run lint-secrets.sh due to a missing `git-secrets` executable on my git server, I decided that now was a good time to use Nix to define my BuildKite pipelines. TL;DR: - Delete ci/scripts directory - Define ci/pipelines/{briefcase,socrates}.nix Outside of this repository: - I logged into my admin account at git.wpcarro.dev and changed my Gitea post-receive hook to trigger the briefcase pipeline - I logged into my BuildKite account, deleted my build-briefcase pipeline, created a new briefcase pipeline that called: ```shell nix-build -A ci.pipelines.briefcase -o briefcase.yaml buildkite-agent pipeline upload briefcase.yaml ``` One day I will audit all of my ad-hoc, non-mono-repo activity (like the steps I listed above) and attempt to fit everything herein... one step at a time, though!
2020-08-21 12:12:57 +02:00
command = ''
nix-build '<nixpkgs/nixos>' \
-I briefcase="$(pwd)" \
-I nixpkgs=/var/lib/buildkite-agent-socrates/nixpkgs-channels \
-I nixos-config=nixos/socrates/default.nix \
-A system \
--no-out-link \
--show-trace
'';
Define Buildkite pipelines corresponding to git server hooks I think maintaining a 1:1 correspondence with the git server hook makes sense right now. Let's try it out!
2020-08-21 19:40:30 +02:00
label = ":nix: build socrates";
depends_on = "build-briefcase";
Define BuildKite pipelines in Nix After a handful of failed attempts to run lint-secrets.sh due to a missing `git-secrets` executable on my git server, I decided that now was a good time to use Nix to define my BuildKite pipelines. TL;DR: - Delete ci/scripts directory - Define ci/pipelines/{briefcase,socrates}.nix Outside of this repository: - I logged into my admin account at git.wpcarro.dev and changed my Gitea post-receive hook to trigger the briefcase pipeline - I logged into my BuildKite account, deleted my build-briefcase pipeline, created a new briefcase pipeline that called: ```shell nix-build -A ci.pipelines.briefcase -o briefcase.yaml buildkite-agent pipeline upload briefcase.yaml ``` One day I will audit all of my ad-hoc, non-mono-repo activity (like the steps I listed above) and attempt to fit everything herein... one step at a time, though!
2020-08-21 12:12:57 +02:00
}
];
Allow configurable BRIEFCASE env var for CI These were hard-coded as $HOME/BRIEFCASE, which won't work in CI, since CI runs as the user buildkite-agent-socrates, whose $HOME directory doesn't exist.
2020-08-31 02:16:31 +02:00
in pkgs.writeText "pipeline.yaml" (toJSON pipeline)
Reference in a new issue Copy permalink