Commit graph

13 commits

Author SHA1 Message Date
Ashwin Kumar Sivakumar
c8fa02a9a4 fix(ci): derive DOCKER_HOST from the job container's own default gateway
Some checks failed
build-and-release / build (push) Failing after 16s
--add-host=host.docker.internal:host-gateway is not being honored by
this act_runner setup (tried via the runner's global container.options
and a per-job container: block; neither worked, confirmed by two
separate failed runs with identical DNS-lookup errors). Read the
container's real default-route gateway from /proc/net/route instead
(portable, no iproute2 dependency) and export it as DOCKER_HOST via
GITHUB_ENV. This is the actual IP of the dind engine that spawned the
job container, regardless of hostname-aliasing support.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 22:50:54 +05:30
Ashwin Kumar Sivakumar
dcf573e0f6 fix(ci): use explicit container: block for reliable job-level docker options
Some checks failed
build-and-release / build (push) Failing after 16s
Forgejo's docs note --add-host via the runner's global
container.options config is not reliably honored for jobs using pure
label-based runs-on mapping. Setting the same image + options
explicitly per-job via jobs.build.container is the more directly
supported path for per-job container customization.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 22:45:35 +05:30
Ashwin Kumar Sivakumar
b9e0ba247c fix(ci): route job-container DOCKER_HOST via host.docker.internal
Some checks failed
build-and-release / build (push) Failing after 16s
127.0.0.1:2375 only worked from the runner container's own network
namespace (sibling to the dind sidecar in the same pod). The actual
job container that runs each step is spawned *by* that dind engine,
one level deeper, so its own loopback doesn't reach the sidecar.
host.docker.internal (mapped to the job container's real gateway via
--add-host=host.docker.internal:host-gateway in the runner's
container.options) reaches back to the dind engine that created it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 19:59:27 +05:30
Ashwin Kumar Sivakumar
0ea4024657 fix(ci): fix YAML syntax error in build.yaml that silently disabled Actions
Some checks failed
build-and-release / build (push) Failing after 14s
The unindented heredoc terminator (<<EOF2 ... EOF2 flush-left) broke the
YAML block-scalar indentation contract for the `run: |` step, causing
Forgejo to log "ignore invalid workflow build.yaml: yaml: line 75:
could not find expected ':'" and silently skip the workflow entirely
on every push since this line was introduced. No builds have run on
main or high-performance since 2026-07-05 as a result. Replaced the
multi-line heredoc with a single-line bash here-string, which needs
no extra indentation and keeps the shell logic identical.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-07 18:34:45 +05:30
Ashwin Kumar Sivakumar
afb4dc9ae6 fix(ci): use docker-ready runner label in Forgejo workflow
- Change runs-on from self-hosted to docker-ready
- Add DOCKER_HOST and DOCKER_BUILDKIT env vars
- Align with other repo workflows
2026-07-06 04:24:06 +05:30
Ashwin Kumar Sivakumar
4bfb5b4418 Update Forgejo backend publish workflow 2026-06-17 03:28:46 +05:30
Ashwin Kumar Sivakumar
349673b7f8 fix(ci): unify backend build flow through forgejo 2026-06-14 01:20:24 +05:30
Ashwin Kumar Sivakumar
0d35bf5649 trigger build: rebuild all services
Some checks failed
build-and-push / detect-changes (push) Successful in 2s
build-and-push / build (catering-services) (push) Failing after 2s
build-and-push / build (companies) (push) Failing after 4s
build-and-push / build (cron) (push) Failing after 3s
build-and-push / build (developers) (push) Failing after 3s
build-and-push / build (customers) (push) Failing after 4s
build-and-push / build (employees) (push) Failing after 3s
build-and-push / build (fitness-trainers) (push) Failing after 4s
build-and-push / build (gateway) (push) Failing after 3s
build-and-push / build (job-seekers) (push) Failing after 3s
build-and-push / build (graphic-designers) (push) Failing after 4s
build-and-push / build (jobs) (push) Failing after 2s
build-and-push / build (leads) (push) Failing after 4s
build-and-push / build (makeup-artists) (push) Failing after 3s
build-and-push / build (payments) (push) Failing after 3s
build-and-push / build (photographers) (push) Failing after 3s
build-and-push / build (tutors) (push) Failing after 3s
build-and-push / build (social-media-managers) (push) Failing after 4s
build-and-push / build (ugc-content-creators) (push) Failing after 3s
build-and-push / build (users) (push) Failing after 4s
build-and-push / build (video-editors) (push) Failing after 3s
2026-06-13 01:23:22 +05:30
Ashwin Kumar Sivakumar
d0b10eac8f trigger forgejo pipeline: rebuild all services
Some checks failed
build-and-push / detect-changes (push) Successful in 4s
build-and-push / build (catering-services) (push) Failing after 3s
build-and-push / build (companies) (push) Failing after 3s
build-and-push / build (cron) (push) Failing after 2s
build-and-push / build (customers) (push) Failing after 4s
build-and-push / build (developers) (push) Failing after 2s
build-and-push / build (fitness-trainers) (push) Failing after 3s
build-and-push / build (employees) (push) Failing after 4s
build-and-push / build (gateway) (push) Failing after 3s
build-and-push / build (graphic-designers) (push) Failing after 3s
build-and-push / build (job-seekers) (push) Failing after 3s
build-and-push / build (jobs) (push) Failing after 3s
build-and-push / build (leads) (push) Failing after 3s
build-and-push / build (makeup-artists) (push) Failing after 3s
build-and-push / build (payments) (push) Failing after 3s
build-and-push / build (social-media-managers) (push) Failing after 3s
build-and-push / build (photographers) (push) Failing after 4s
build-and-push / build (tutors) (push) Failing after 3s
build-and-push / build (ugc-content-creators) (push) Failing after 3s
build-and-push / build (users) (push) Failing after 3s
build-and-push / build (video-editors) (push) Failing after 4s
build-and-push / cleanup-after-build (push) Failing after 0s
Retention script was too aggressive and deleted most images.
Increasing keep count from 2 to 10 SHA tags.
2026-06-12 23:55:01 +05:30
Ashwin Kumar Sivakumar
0bda2b2f10 remove: delete high-performance-latest tag from builds - use SHA tags only 2026-06-12 04:40:36 +05:30
Ashwin Kumar Sivakumar
8adc84699e fix: keep only 2 SHA tags (current + 1 previous) to save disk space 2026-06-12 04:12:15 +05:30
Ashwin Kumar Sivakumar
758f0699ff fix: move image cleanup to post-build job after all builds complete 2026-06-12 04:10:52 +05:30
Ashwin Kumar Sivakumar
1b1d98ebee chore: migrate ci naming to forgejo 2026-06-11 17:17:42 +05:30
Renamed from .gitea/workflows/build.yaml (Browse further)