Skip to content

ci(jenkins): skip Windows executable signing when RUN_CHOCOLATEY is disabled - #3520

Merged
BlasttS merged 1 commit into
masterfrom
skip-windows-signing-when-no-choco
May 28, 2026
Merged

BlasttS merged 1 commit into
masterfrom
skip-windows-signing-when-no-choco

Conversation

@ehl-jf

@ehl-jf ehl-jf commented May 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Gate the Windows signing block in build() on params.RUN_CHOCOLATEY so the Docker-based signing step is skipped on runs that don't publish to Chocolatey.
  • Also skip downloadToolsCert() in that case, since the cert is only consumed by the (now-skipped) Windows signing step.

When RUN_CHOCOLATEY=true (the default), behavior is unchanged. When it is disabled, the standalone Windows .exe uploaded by uploadCli will be unsigned — intended for dev/test runs without access to the signing infrastructure.

Test plan

  • Run the Jenkins job with RUN_CHOCOLATEY=false and confirm no signing/cert download stages execute and the Windows binary uploads succeed.
  • Run the Jenkins job with RUN_CHOCOLATEY=true and confirm signing still happens for both the standalone Windows exe and the Chocolatey package.

…isabled

Gate the Windows signing block in build() and the downloadToolsCert()
call on params.RUN_CHOCOLATEY so dev/test runs without the Chocolatey
stage don't require the signing cert and Docker-based signing step.
@ehl-jf ehl-jf added the ignore for release Automatically generated release notes label May 28, 2026
@BlasttS
BlasttS merged commit 5cfd613 into master May 28, 2026
34 of 35 checks passed
@BlasttS
BlasttS deleted the skip-windows-signing-when-no-choco branch May 28, 2026 08:47

This branch had an error being deployed

1 failed deployment
frogbot — ee1c97f2 Deployed May 28, 2026 by ehl-jf via scan-pull-request #4347
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ignore for release Automatically generated release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants