Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DevOps: Investigate why deploy to Fly.io not working ... #327

Open
1 task
nelsonic opened this issue Mar 2, 2023 · 2 comments
Open
1 task

DevOps: Investigate why deploy to Fly.io not working ... #327

nelsonic opened this issue Mar 2, 2023 · 2 comments
Labels
chore a tedious but necessary task often paying technical debt priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished research Research required; be specific T2h Time Estimate 2 Hours tech-debt A feature/requirement implemented in a sub-optimal way & must be re-written technical A technical issue that requires understanding of the code, infrastructure or dependencies

Comments

@nelsonic
Copy link
Member

nelsonic commented Mar 2, 2023

Sadly the latest build/deploy to Fly.io errored: https://github.com/dwyl/mvp/actions/runs/4294285365/jobs/7483140257#step:4:1528

Todo

  • Investigate why and document as much as possible so we can avoid this in the future. 🙏

priority-2 because we haven't released any new features this week. 🎻
but it still important to fix the deployment so that when we release new stuff it works. 👌
@nelsonic nelsonic added T2h Time Estimate 2 Hours technical A technical issue that requires understanding of the code, infrastructure or dependencies priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished chore a tedious but necessary task often paying technical debt research Research required; be specific tech-debt A feature/requirement implemented in a sub-optimal way & must be re-written labels Mar 2, 2023
@LuchoTurtle
Copy link
Member

This looks like it was a one-off issue, as merging 406c2b6 succeeded right after.

I remember re-running this action (after seeing this issue) and deploying correctly.

I can't place what exactly happened (it might have been networking or DNS issues - as it happened in
https://community.fly.io/t/error-release-command-failed-deployment-aborted/2918/13) but it resolved in itself 💭

@nelsonic
Copy link
Member Author

nelsonic commented Apr 4, 2023

Thanks for confirming @LuchoTurtle 👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chore a tedious but necessary task often paying technical debt priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished research Research required; be specific T2h Time Estimate 2 Hours tech-debt A feature/requirement implemented in a sub-optimal way & must be re-written technical A technical issue that requires understanding of the code, infrastructure or dependencies
Projects
dwyl app kanban
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@nelsonic @LuchoTurtle