john/runtimeterror
1
0
Fork 0
mirror of https://github.com/jbowdre/runtimeterror.git synced 2024-11-24 16:02:18 +00:00
Code Issues Projects Releases Packages Wiki Activity

Compare commits

base: john:7f97dfadd24f93e6c3791774225fd017549a9162
Branches Tags
john:main
john:drafts
john:preview
..
compare: john:c3b39f26895085f9fbf7df64a7029d4e51291a0f
Branches Tags
john:main
john:drafts
john:preview

No commits in common. "7f97dfadd24f93e6c3791774225fd017549a9162" and "c3b39f26895085f9fbf7df64a7029d4e51291a0f" have entirely different histories.
7f97dfadd2 ... c3b39f2689

1 changed files with 1 additions and 2 deletions
Show stats Expand all files Collapse all files

3
content/posts/automate-packer-builds-github-actions/index.md
View file

@ -135,7 +135,7 @@ For more examples and ideas, visit:
So the Docker piece is sorted; now for setting up the runner.
#### Install/Configure Runner
I know I've been talking about a singular runner, but I'm actually setting up multiple instances of the runner on the same host to allow running jobs in parallel. I could probably support four simultaneous builds in my homelab but I'll start with just two runners for now (after all, I only have two build flavors so far anyway).
I know I've been talking about a singular runner, but I'm actually seting up multiple instances of the runner on the same host to allow running jobs in parallel. I could probably support four simultaneous builds in my homelab but I'll settle two runners for now (after all, I only have two build flavors so far anyway).
Each runner instance needs its own directory so I create those under `/opt/github/`:
@ -438,7 +438,6 @@ If it fails for some reason, the `Retry on failure` step will try again, just in
Here's the complete `.github/workflows/build.yml`, all in one code block:
```yaml
# torchlight! {"lineNumbers":true}
name: Build VM Templates
on: