infrastructure automatically deployed using continuous deployment #177
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
2 participants
Notifications
Due date
No due date set.
Blocks
#69 Separate test environments for staging vs. production
fediversity/fediversity
#224 automated dev-ops workflows
fediversity/fediversity
#302 code reviewers can suggest changes
fediversity/fediversity
Reference: fediversity/fediversity#177
Loading…
Add table
Add a link
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 commits to main to be deployed automatically,
so that we can more easily demonstrate our progress to non-developers.
Acceptance criteria
Given a PR change to our infrastructure code,
When I merge the PR,
The infrastructure is realized as described by that code.
continuous deploymentto infrastructure automatically deployed using continuous deploymentas per run https://git.fediversity.eu/Fediversity/Fediversity/actions/runs/1017#jobstep-3-102, this seems to get stuck now at:
i presume this would be resolved with #309, tho the TF thread we had de-prioritized in favor of #103.
But is it stuck consistently? And maybe it's some resource bottleneck like thrashing due to lack of swap? It doesn't look like a failure mode that has anything to do with nixops.
to be fair now it got stuck at some different part.
topanddfqueries also revealed no weird resource usage, nor didsystemctlorjournalctl -xeshow anything off on theforgejo-cinode.okay, there may be a few different things on our roadmap that could impact this:
my procolix colleague Jonathan further offered assistance in debugging this CI flaking. potentially
straceing the process could help with this.an
htopattempt by Jonathan showed it as stuck on:to debug further we used
nixops4's verbose mode, which in turn revealed it as hanging on:that echo command appears part of at least
nix copy, and seems to have hit various other users before.some clues i'm gleaning from others affected:
SHELLset to e.g.${pkgs.bash}/bin/bashfrom the deploying nodeSHELLenv var in CD #466CD went thru 🥳
https://git.fediversity.eu/Fediversity/Fediversity/actions/runs/1031