Skip to content

fix(CI-23237): use CI-23237 branch for RF GitClone in harness.yaml - #520

Open
imaditya55 wants to merge 8 commits into
masterfrom
CI-23237
Open

fix(CI-23237): use CI-23237 branch for RF GitClone in harness.yaml#520
imaditya55 wants to merge 8 commits into
masterfrom
CI-23237

Conversation

@imaditya55

Copy link
Copy Markdown
Collaborator

(temp debug build)

Temporarily point the four RapidFort GitClone steps at the CI-23237 branch so drone-docker-harness can build harnesssecure/gar with the cosign bump before the ci-rapidfort-plugins PR merges to main.

imaditya55 and others added 8 commits July 17, 2026 15:58
…emp debug build)

Temporarily point the four RapidFort GitClone steps at the CI-23237 branch
so drone-docker-harness can build harnesssecure/gar with the cosign bump
before the ci-rapidfort-plugins PR merges to main.

Co-authored-by: Cursor <cursoragent@cursor.com>
golang:1.25.7 has no Windows Server 1809 container manifest.
Revert win-1809-amd64 and win-1809-amd64-rf to golang:1.23.0,
matching the CI-23243 ECR approach, so the tag pipeline can complete.
…cure/gar

Updates golang.org/x/crypto, golang.org/x/net, aws-sdk-go-v2, and
google.golang.org/api for gar5 debug build / OnDemand rescan.
…images

Add RF Push Docker Base and tag push steps on rf-linux-amd64/arm64 so
harnesssecure/gar can FROM harnesssecure/docker:linux-amd64|arm64.
Wrapper matrix now only pushes acr/ecr/gar after the base is published.

Co-authored-by: Cursor <cursoragent@cursor.com>
now the main branch has both the new updated cosign version and the harnesssecure/docker
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