NixOS test of a deployment #276
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Blocks
#65 Automated dependency updates
fediversity/fediversity
#102 CI rejects failing deployments
fediversity/fediversity
#224 automated dev-ops workflows
fediversity/fediversity
#277 integration test panel
fediversity/fediversity
Reference
fediversity/fediversity#276
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?
NixOS test that runs NixOps4 on a deployment generated with our code, the checks that the appropriate configurations have been pushed in the right place.
This is basically just a variant of the existing nixops4-nixos test (permalink) on our own code.
c.f. #323, which iiuc addressed this in part (and provided an update on current status)
kiara referenced this issue2025-05-05 19:48:02 +02:00
nixops4 apply#329Closed by Fediversity/Fediversity#329