CI rejects failing deployments #102
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
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#224 automated dev-ops workflows
fediversity/fediversity
#101 Deploy Fediversity Panel
fediversity/fediversity
#276 NixOS test of a deployment
fediversity/fediversity
#323 Add a basic integration test
fediversity/fediversity
Reference
fediversity/fediversity#102
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 contributor to this project, whenever I make changes to deployed services, CI should prevent merging PRs if that deployment would fail.
this might include:
closing in favor of #276, #277
kiara referenced this issue2025-06-10 20:19:14 +02:00
we currently have tests covering this