Skip to content

ci: publish sitmun-shared to mavenLocal before build - #21

Merged
fjlopez merged 1 commit into
devfrom
fix/ci-publish-sitmun-shared
Oct 8, 2026
Merged

fjlopez merged 1 commit into
devfrom
fix/ci-publish-sitmun-shared

Conversation

@fjlopez

@fjlopez fjlopez commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

Why

Proxy CI could not resolve org.sitmun:sitmun-proxy-contract:1.2.9. The configuration-cache error was a symptom of that missing artifact. The monitoring change added the dependency and mavenLocal(), but CI never published sitmun-shared.

What changed

  • Clone and publishToMavenLocal for sitmun-shared before Gradle in CI and CodeQL, matching backend-core.

Scope

  • Covers proxy CI and CodeQL assemble on dev.
  • Does not change application code or disable configuration-cache.

Tradeoffs

  • Mirror the backend-core workflow step instead of publishing the contract to a remote repository. Same pattern already works there.

Blast Radius

  • Workflow-only. Local builds that already have the contract in mavenLocal stay the same. Leaving dev red blocks proxy merges.

Verification

  • CI log for run 37548591074. Could not find org.sitmun:sitmun-proxy-contract:1.2.9.
  • Local ./gradlew build -x setupGitHooks after the workflow edit. BUILD SUCCESSFUL.
  • GitHub Actions on this PR is the real proof for the publish step.

compileClasspath needs org.sitmun:sitmun-proxy-contract from
mavenLocal, which CI never published. Mirror the backend-core
workflow step so CI and CodeQL assemble can resolve it.
@fjlopez
fjlopez merged commit 4624918 into dev Oct 8, 2026
3 checks passed
@fjlopez
fjlopez deleted the fix/ci-publish-sitmun-shared branch October 8, 2026 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant