-
Notifications
You must be signed in to change notification settings - Fork 91
fix(ci): replace gitParameter with string parameter #19234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Jenkins BuildsClick to see older builds (19)
|
7cc7ade to
30ac3c2
Compare
Recent upgrade of Jenkins and Git Paramter plugin caused these to appear: [2025-11-07T12:07:08.487Z] Scheduling project: status-desktop » e2e » prs Invalid parameter value: (StringParameterValue) GIT_REF='6e42ff2a5cb10933332d6722e1c19babc9973c07' Which are caused by recently patched vulnerability in the plugin: https://www.jenkins.io/security/advisory/2025-07-09/#SECURITY-3419 https://github.com/jenkinsci/git-parameter-plugin/releases/tag/444.vca_b_84d3703c2 We could disable this check with: gitParameterDefinition.allowAnyParameterValue=true But just using a String paramater is simpler and more convenient. Signed-off-by: Jakub Sokołowski <jakub@status.im>
30ac3c2 to
5fbadab
Compare
|
Keep in mind feature branches will have to rebase to take effect. |
I've rebased by branch, but the error is the same https://ci.status.im/blue/organizations/jenkins/status-desktop%2Fprs%2Fwindows%2Fx86_64%2Fpackage/detail/PR-19116/7/pipeline git log: |
|
Using |
|
That change doesn't make sense. We want to test an exact commit, not the branch. But it works as a temp fix to let it run. |
Recent upgrade of Jenkins and Git Paramter plugin caused these to appear:
Which are caused by recently patched vulnerability in the plugin:
We could disable this check with:
But just using a String paramater is simpler and more convenient.