Skip to content

Pipeline upload: look for secrets within trigger step build.env - #4116

Open
DrJosh9000 wants to merge 1 commit into
mainfrom
inspect-trigger-build-env
Open

Pipeline upload: look for secrets within trigger step build.env#4116
DrJosh9000 wants to merge 1 commit into
mainfrom
inspect-trigger-build-env

Conversation

@DrJosh9000

Copy link
Copy Markdown
Contributor

Description

Trigger steps can contain env blocks too: under build. In pipeline upload, include these in the secret search.

Context

Buildsworth outputted some tokens upon the v4 branch: #3807 (comment)

Testing

  • Tests have run locally (with go test ./...). Buildkite employees may check this if the pipeline has run automatically.
  • Code is formatted (with go tool gofumpt -extra -w .)

Disclosures / Credits

I happen to know how this works.

@DrJosh9000
DrJosh9000 requested review from a team as code owners July 22, 2026 07:43
@DrJosh9000 DrJosh9000 added the bug label Jul 22, 2026

@buildsworth-bk-app buildsworth-bk-app Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found. This changes pipeline-upload secret detection, so I’m leaving the final call to a human reviewer.

Want to dig deeper?

The full session log is attached to this Buildkite build. Download the session file and open a new pi session with it:

Download the buildsworth logs from build 7127, then answer my questions about the findings.

@DrJosh9000
DrJosh9000 enabled auto-merge July 22, 2026 07:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant