Skip to content

build: derive the WebRTC cache branch from the pom and guard deploys - #248

Merged
devopvoid merged 1 commit into
devopvoid:mainfrom
SendableMetatype:ci/fork-safe-ci
Aug 11, 2026
Merged

build: derive the WebRTC cache branch from the pom and guard deploys#248
devopvoid merged 1 commit into
devopvoid:mainfrom
SendableMetatype:ci/fork-safe-ci

Conversation

@SendableMetatype

Copy link
Copy Markdown
Contributor

Two CI robustness issues in one commit:

The WebRTC cache branch is pinned as a literal env in the workflows and must be kept in sync with webrtc-jni/pom.xml by hand; when they drift, lanes restore caches for the wrong engine branch. A setup step now derives the value from the pom, making the pom the single source of truth.

The Sonatype deploy steps run unconditionally, so on any fork every fully successful lane concludes as failure from the credentialless 401, and because cache saves are gated on success, fork builds can never warm their caches either. Deploys are now skipped on pull requests and guarded to the devopvoid/webrtc-java repository. Behavior for this repository's own pushes is unchanged.

@devopvoid
devopvoid merged commit 81b725c into devopvoid:main Aug 11, 2026
17 of 19 checks passed
@SendableMetatype
SendableMetatype deleted the ci/fork-safe-ci branch August 12, 2026 15:33
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.

2 participants