ci: remove dead build-dependency-image workflow [DEVX-3181] - #31
Merged
Conversation
This workflow required the `tools-runner` self-hosted runner, but the runner group that provides it does not grant access to public repos, so the job hung in `queued` forever with no runner assigned. It also targeted the internal JENKINS_INTERNAL_URL, unreachable from a public repo's runners. The trigger has been moved to draios/secure-backend (private, has secure-runner access and the Jenkins secrets) as a manual workflow_dispatch: .github/workflows/compliance-linux-bench-dependency.yml Tag creation for linux-bench dependency releases stays here (git tag + push); publishing the image is now done from secure-backend against that tag. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
haresh-suresh
approved these changes
Jul 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This workflow required the
tools-runnerself-hosted runner, but the runner group that provides it does not grant access to public repos, so the job hung inqueuedforever with no runner assigned. It also targeted the internal JENKINS_INTERNAL_URL, unreachable from a public repo's runners.The trigger has been moved to draios/secure-backend (private, has secure-runner access and the Jenkins secrets) as a manual workflow_dispatch: .github/workflows/compliance-linux-bench-dependency.yml
Tag creation for linux-bench dependency releases stays here (git tag + push); publishing the image is now done from secure-backend against that tag.