perso/mcp-ics
4
0 Fork 0
Code Issues 1 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

ci: align pipeline on web/mydl pattern (real docker tags) #27

Merged
jcabillot merged 2 commits from ci/align-mydl into main 2026-10-08 16:54:05 -04:00
Conversation 1 Commits 2 Files Changed 7
+151 -63
2 Commits
Author SHA1 Message Date
OpenCode Cabillot 155178c665 ci: smoke test = compileall (server.py raises on import without CALDAV_DATA_PATH)
CI Shared Jobs / hadolint (pull_request) Successful in 41s
Details
CI Shared Jobs / build-test (pull_request) Successful in 3m38s
Details
PR Checks / ci (pull_request) Successful in 4m40s
Details
2026-10-08 20:40:10 +00:00
OpenCode Cabillot b71e470511 ci: align pipeline on web/mydl pattern
CI Shared Jobs / hadolint (pull_request) Successful in 3m43s
Details
CI Shared Jobs / build-test (pull_request) Failing after 4m10s
Details
PR Checks / ci (pull_request) Failing after 4m20s
Details 
Split the monolithic docker-build/release/test workflows into the shared
_ci-common.yaml + trigger-specific files used on web/mydl:

- pr.yaml       -> PR checks (hadolint + build smoke test)
- main.yaml     -> CI + local build + git semver tag (PAT, triggers tag.yaml)
- tag.yaml      -> CI + build/push :vX.Y.Z and :vX.Y.Z-latest (sole Docker push)
- cron.yaml     -> nightly rebuild of :vX.Y.Z-latest
- _ci-common.yaml -> hadolint + build-test with docker smoke and GHA cache

Docker pushes to :latest on every merge are replaced by versioned,
tested tags. The tag job uses SA_TOKEN_ACTION_PUSH_TAGS (a PAT) so the
tag push actually triggers tag.yaml - GITHUB_TOKEN would not.
 2026-10-08 20:29:23 +00:00