unit-tested functionality integrated in deployment pipelines #833
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
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
1 participant
Notifications
Due date
No due date set.
Blocks
#69 Separate test environments for staging vs. production
fediversity/fediversity
#116 hypervisor resources are provisioned to deploy services to
fediversity/fediversity
#200 reproduce DNS VM
fediversity/fediversity
#336 reproducible project infrastructure
fediversity/fediversity
#433 deployment provisions host infra
fediversity/fediversity
#724 LXC container deployment
fediversity/fediversity
Reference
fediversity/fediversity#833
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?
split out from #309:
proxmoxincusafterwards, each of these should still be added to our infra too (may have separate tickets).
note that use of non-operator nodes there may raise questions on having to settle for client-side over server-side configuration.
tf-proxmox-hosts#845