Add CI builds to a public cache #92
Labels
No labels
blocked
bug
component: fediversity panel
component: nixops4
contributor experience
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
goal: devops
project-management
question
role: sysadmin
security
technical debt
testing
user experience
user story
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Fediversity/Fediversity#92
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This will make it much easier to onboard to the project either as a user or contributor.
@roberth > Do you have anything set up at least for NixOps4, the version of Nix you rely on, the providers, etc.? A cache somewhere that we could recommend in our README?
I've set up https://nixops4.cachix.org, written to by a Hercules CI agent that I run for the https://github.com/nixops4 org.
It's not a particularly long build, so I haven't bothered documenting the existence of this cache.
I don't think it's particularly relevant to Fediversity either, because a build will end up in the Fediversity cache anyway.
Indeed; but seeing as there is no Fediversity cache for now, that could give us a small gain in the meantime.
c.f. #155