Add testnet CI/CD workflow, consolidate production workflows (Option A) #73
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/cicd-option-a"
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?
registry, pulls and restarts on testnet VM via SSH, runs health check
single workflow for release tags (excludes -rc), includes build, push,
k8s deploy, health check, smoke tests, and release creation
deploy-production.yml
CI/CD flow:
New secret required: TESTNET_SSH_KEY (SSH key for testnet VM, port 34022)
@ -96,2 +156,3 @@env:FORGEJO_TOKEN: ${{ github.token }}run: |./scripts/gateway-smoke-test.sh https://ledger.dev.projectmycelium.comWas this intentional?
@ -0,0 +121,4 @@# Wait for healthyecho 'Waiting for container to be healthy...'for i in \$(seq 1 30); doSTATUS=\$(sudo docker inspect --format='{{.State.Health.Status}}' deploy-portal-1 2>/dev/null || echo 'starting')The current Dockerfile has no HEALTHCHECK directive, so
.State.Health.Statuswould be empty/missing. The check would fall through to the external curl health check, which does work but the docker inspect loop is dead code and wasting a minute of waiting.See please here #72 (comment)
@ -21,1 +22,4 @@tags:- "v*"- "!v*-rc*"workflow_dispatch:I would remove workflow_dispatch from testnet entirely.
The intended flow is: push a tag → deploy. If you need to redeploy a version, push the same tag again (force) or delete and recreate it. Manual dispatch adds complexity for a use case that the tag flow already covers.
Attached patch applies on top of this PR's branch:
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.