Document how to build a NixOS system toplevel
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- nixos
- Domain
- build-system, documentation
Research direction
Review Hydra's existing examples and documentation for NixOS build workflows, then identify where the system-toplevel use case belongs. Document how to build system toplevels and push the relevant artefacts to the local S3 store so deployed systems can retrieve them without building locally.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Hydra seems to be great for building nixpkgs, or a subset of this. I've deployed my own Hydra and have my own local S3 cluster and the two work great.
However, I do not wish to build the (multi-TB) entirety of nixpkgs as my systems deployments requires a significantly tiny number of packages within this.
Instead, I'd like to use Hydra to simply build my systems' toplevels and push the relevant artefacts to the S3 store - then my systems can pull those down without having to do any parts of the builds themselves.
However, this usecase isn't documented in the examples.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 365
- Avg merge
- 15h 37m
- Merged PRs (30d)
- 61
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NixOS/hydra
-
queue runner
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NixOS/hydra#1796 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 40/100
Maintainers usually reply within 1 day
Similar issues
-
check-skill-pages: show fixture build errors when a build failsPossibly taken @ShahadatTest claimed this today. Opengood first issue P2
Difficulty 1/5 Under an hour Newbie friendliness 85/100
coco-research/coco#439 · 1 comment ·
Maintainers usually reply within 1 day
-
CI enhancement good first issue help wanted P2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
yesvus/helmdeck#449 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ssrajadh/sentrysearch#104 ·
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mnemosyne-oss/mnemosyne#1317 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
confident-ai/deepteam#300 ·
Maintainers usually reply within 1 day