Hi Danny et al,
I think, I just stumbled over the same problem:
One possible workaround – that might be OK if there are very few affected parameterized pipelines, or the parameterization is fairly stable, or there are just very few different paramaterizations – seems to be duplicating the parameterization into the JobDSL specification of the pipeline, for example:
properties([
parameters([
string(name: 'targetHost', defaultValue: 'my.host.com', description: 'IP/Hostname of target server', trim: true)
])
])
pipelineJob(" My pipeline JobName") {
// Workaround for https://issues.jenkins.io/browse/JENKINS-43758?focusedCommentId=380158&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-380158
parameters {
stringParam('targetHost', 'my.host.com', 'IP/Hostname of target server')
}
definition {
cpsScm {
...
Are there any updates on this problem?
Or are there open Jenkins (plugin) issues that really address this problem? Or should we file a new one specific for this problem? (If so, I am not even sure for which Jenkins plugin, to be perfectly honest.)
Or is there a better workaround?
Thanks,
Reinhold
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/WRZAIQ.I9W7CPAM6YSS%40gmail.com.