Continuous Integration builds available in a public cache #92
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Blocks
Depends on
#288 external developers empowered to contribute
fediversity/fediversity
#954 demo env broken
fediversity/fediversity
Reference
fediversity/fediversity#92
Loading…
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?
As a developer,
I want for Continuous Integration builds to be available in a public cache,
so that I may get the code running more easily.
implementation notes
this can be done safely using:
atticcellerniks3nix-cache-beaconas per #155 (comment), we should have an isolated instance that will run builds on PRs, read-only accessing the main cache and not caching build results (or only between PR rebuilds), and another instance that runs builds on
mainand caches build results publicly.@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
edit: caching notes
Add CI builds to a public cacheto Continuous Integration builds available in a public cache