Thanks for your responses Gavin Mogan and slide.
When I tried to remove the parameter from the @DataBoundConstructor and
added a second @DataBoundSetter like:
@DataBoundSetter
public void setImportTowerLogs(Boolean importTowerLogs) {
this.importTowerLogs = importTowerLogs.toString(); }
@DataBoundSetter
public void setTImportTowerLogs(String importTowerLogs) {
this.importTowerLogs = importTowerLogs; }
both pipelines worked with the constructor but only the second
@DataBoundConstructor would be honored.
To solve my problem I removed the parameter from the @DataBoundConstructor
and then replaced the old Boolean importTowerLogs with String towerLogLevel
with the exception that I left the @DataBoundConstructor for importTowerLog
as:
@DataBoundSetter
public void setImportTowerLogs(Boolean importTowerLogs) { this.towerLogLevel
= importTowerLogs.toString(); }
Things now seem to work fine for both the old boolean parameter like
importTowerLogs = {true|false} or with a new string parameter like
towerLogLevel = {'true'|'false'|'vars'|'full'}.
-John
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/d264323c-7a8d-48a4-af50-a526a46633ddo%40googlegroups.com.
