You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I create a job following the ReadMe guide, set ${gitlabSourceBranch} to Branch Specifier.
However, it failed while pulling the source branch.
> git -c core.askpass=true fetch --tags --progress ssh://git@*** HIDDEN **.git +refs/heads/:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10
> git rev-parse refs/remotes/origin/refs/remotes/origin/${gitlabSourceBranch}^{commit} # timeout=10
> git rev-parse refs/remotes/origin/${gitlabSourceBranch}^{commit}
# timeout=10
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Finished: FAILURE
It seems that params are undefined, After google for a long time, I figureout that it is jenkins's security update. Detail:https://jenkins.io/blog/2016/05/11/security-update/.
I define the following system properties to work around this limitation, and it works
Set hudson.model.ParametersAction.keepUndefinedParameters to true, e.g.java -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar jenkins.war to revert to the old behavior of allowing any build parameters. Depending on your environment, this may be unsafe, as it opens you up to attacks as described above.
Set hudson.model.ParametersAction.safeParameters to a comma-separated list of safe parameter names, e.g. java -Dhudson.model.ParametersAction.safeParameters=FOO,BAR_baz,quX -jar jenkins.war.
The text was updated successfully, but these errors were encountered:
I create a job following the ReadMe guide, set
${gitlabSourceBranch}
toBranch Specifier
.However, it failed while pulling the source branch.
It seems that params are undefined, After google for a long time, I figureout that it is jenkins's security update. Detail:https://jenkins.io/blog/2016/05/11/security-update/.
I define the following system properties to work around this limitation, and it works
The text was updated successfully, but these errors were encountered: