• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: list-git-branches-parameter-plugin
• Labels:

  • configuration
  • git
  • jenkins
  • plugin
• Environment:

  Jenkins Version: 2.361.1
  List Git Branches Parameter Plugin Version: 0.0.11
  Red Hat Enterprise Linux

[JENKINS-69771] 0.0.11 release breaks compatibility to 0.0.9 or earlier Jenkinsfile parameter

James Zhu created issue - 2022-10-04 05:15

James Zhu made changes - 2022-10-04 05:16

Description

Original: This fix: [Fix default listSize by rob-ott - Pull Request #13 - jenkinsci/list-git-branches-parameter-plugin - GitHub|https://github.com/jenkinsci/list-git-branches-parameter-plugin/pull/13/files] Released as part of 0.0.11 breaks pipeline Jenkinsfile setup in 0.0.9 or earlier versions where the listSize parameter was not required. If you try to load a jenkinsfile using list-git-branches-parameter with no listSize parameter in a Jenkins with the 0.0.11 version of the plugin installed Jenkins will throw this error when creating pipeline: !image-2022-10-04-16-08-31-953.png! Conversely, if you try to load a pipeline Jenkinsfile using list-git-branches-parameter with a listSize parameter in Jenkins running 0.0.9 version of the plugin, Jenkins will also throw an error when creating pipeline: !image-2022-10-04-16-07-03-007.png|width=1266,height=101! In organisation where pipeline files are version controlled and dynamically loaded into Jenkins to populate jobs it may be unavoidable to have jobs that want to call the plugin both ways due to Jenkins loading older jenkinsfile as part of a past release tag. Therefore ideally the plugin should handle both cases where listSize could be supplied or may be missing, possibly via overloading the method to make listSize optional.

New: This fix: [Fix default listSize by rob-ott - Pull Request #13 - jenkinsci/list-git-branches-parameter-plugin - GitHub|https://github.com/jenkinsci/list-git-branches-parameter-plugin/pull/13/files] Released as part of 0.0.11 breaks pipeline Jenkinsfile setup in 0.0.9 or earlier versions where the listSize parameter was not required. If you try to load a jenkinsfile using list-git-branches-parameter with no listSize parameter in a Jenkins with the 0.0.11 version of the plugin installed Jenkins will throw this error when creating pipeline: !image-2022-10-04-16-16-01-852.png! Conversely, if you try to load a pipeline Jenkinsfile using list-git-branches-parameter with a listSize parameter in Jenkins running 0.0.9 version of the plugin, Jenkins will also throw an error when creating pipeline: !image-2022-10-04-16-16-16-399.png! In organisation where pipeline files are version controlled and dynamically loaded into Jenkins to populate jobs it may be unavoidable to have jobs that want to call the plugin both ways due to Jenkins loading older jenkinsfile as part of a past release tag. Therefore ideally the plugin should handle both cases where listSize could be supplied or may be missing, possibly via overloading the method to make listSize optional.

James Zhu made changes - 2022-10-04 05:17

Description

Original: This fix: [Fix default listSize by rob-ott - Pull Request #13 - jenkinsci/list-git-branches-parameter-plugin - GitHub|https://github.com/jenkinsci/list-git-branches-parameter-plugin/pull/13/files] Released as part of 0.0.11 breaks pipeline Jenkinsfile setup in 0.0.9 or earlier versions where the listSize parameter was not required. If you try to load a jenkinsfile using list-git-branches-parameter with no listSize parameter in a Jenkins with the 0.0.11 version of the plugin installed Jenkins will throw this error when creating pipeline: !image-2022-10-04-16-16-01-852.png! Conversely, if you try to load a pipeline Jenkinsfile using list-git-branches-parameter with a listSize parameter in Jenkins running 0.0.9 version of the plugin, Jenkins will also throw an error when creating pipeline: !image-2022-10-04-16-16-16-399.png! In organisation where pipeline files are version controlled and dynamically loaded into Jenkins to populate jobs it may be unavoidable to have jobs that want to call the plugin both ways due to Jenkins loading older jenkinsfile as part of a past release tag. Therefore ideally the plugin should handle both cases where listSize could be supplied or may be missing, possibly via overloading the method to make listSize optional.

New: This fix: [Fix default listSize by rob-ott - Pull Request #13 - jenkinsci/list-git-branches-parameter-plugin - GitHub|https://github.com/jenkinsci/list-git-branches-parameter-plugin/pull/13/files] Released as part of 0.0.11 breaks pipeline Jenkinsfile setup in 0.0.9 or earlier versions where the listSize parameter was not required. If you try to load a jenkinsfile using list-git-branches-parameter with no listSize parameter in a Jenkins with the 0.0.11 version of the plugin installed Jenkins will throw this error when creating pipeline: !image-2022-10-04-16-16-01-852.png! Conversely, if you try to load a pipeline Jenkinsfile using list-git-branches-parameter with a listSize parameter in Jenkins running 0.0.9 version of the plugin, Jenkins will also throw an error when creating pipeline:     ??*12:03:57*?? ERROR: (unknown source) No signature of method: listSize() is applicable for argument types: (java.lang.String) values: [5] ??*12:03:57*?? Possible solutions: name(), description(), remoteURL(), credentialsId(), defaultValue(), sortMode(), selectedValue(), quickFilterEnabled(), type(), tagFilter(), branchFilter() ??*12:03:57*?? Finished: FAILURE   In organisation where pipeline files are version controlled and dynamically loaded into Jenkins to populate jobs it may be unavoidable to have jobs that want to call the plugin both ways due to Jenkins loading older jenkinsfile as part of a past release tag. Therefore ideally the plugin should handle both cases where listSize could be supplied or may be missing, possibly via overloading the method to make listSize optional.

James Zhu made changes - 2022-10-04 05:18

Description

Original: This fix: [Fix default listSize by rob-ott - Pull Request #13 - jenkinsci/list-git-branches-parameter-plugin - GitHub|https://github.com/jenkinsci/list-git-branches-parameter-plugin/pull/13/files] Released as part of 0.0.11 breaks pipeline Jenkinsfile setup in 0.0.9 or earlier versions where the listSize parameter was not required. If you try to load a jenkinsfile using list-git-branches-parameter with no listSize parameter in a Jenkins with the 0.0.11 version of the plugin installed Jenkins will throw this error when creating pipeline: !image-2022-10-04-16-16-01-852.png! Conversely, if you try to load a pipeline Jenkinsfile using list-git-branches-parameter with a listSize parameter in Jenkins running 0.0.9 version of the plugin, Jenkins will also throw an error when creating pipeline:     ??*12:03:57*?? ERROR: (unknown source) No signature of method: listSize() is applicable for argument types: (java.lang.String) values: [5] ??*12:03:57*?? Possible solutions: name(), description(), remoteURL(), credentialsId(), defaultValue(), sortMode(), selectedValue(), quickFilterEnabled(), type(), tagFilter(), branchFilter() ??*12:03:57*?? Finished: FAILURE   In organisation where pipeline files are version controlled and dynamically loaded into Jenkins to populate jobs it may be unavoidable to have jobs that want to call the plugin both ways due to Jenkins loading older jenkinsfile as part of a past release tag. Therefore ideally the plugin should handle both cases where listSize could be supplied or may be missing, possibly via overloading the method to make listSize optional.

New: This fix: [Fix default listSize by rob-ott - Pull Request #13 - jenkinsci/list-git-branches-parameter-plugin - GitHub|https://github.com/jenkinsci/list-git-branches-parameter-plugin/pull/13/files] Released as part of 0.0.11 breaks pipeline Jenkinsfile setup in 0.0.9 or earlier versions where the listSize parameter was not required. If you try to load a jenkinsfile using list-git-branches-parameter with no listSize parameter in a Jenkins with the 0.0.11 version of the plugin installed Jenkins will throw this error when creating pipeline: !image-2022-10-04-16-16-01-852.png! Conversely, if you try to load a pipeline Jenkinsfile using list-git-branches-parameter with a listSize parameter in Jenkins running 0.0.9 version of the plugin, Jenkins will also throw an error when creating pipeline:{{{}{}}} {code:java} 12:03:57 ERROR: (unknown source) No signature of method: listSize() is applicable for argument types: (java.lang.String) values: [5] 12:03:57 Possible solutions: name(), description(), remoteURL(), credentialsId(), defaultValue(), sortMode(), selectedValue(), quickFilterEnabled(), type(), tagFilter(), branchFilter() 12:03:57 Finished: FAILURE {code}   In organisation where pipeline files are version controlled and dynamically loaded into Jenkins to populate jobs it may be unavoidable to have jobs that want to call the plugin both ways due to Jenkins loading older jenkinsfile as part of a past release tag. Therefore ideally the plugin should handle both cases where listSize could be supplied or may be missing, possibly via overloading the method to make listSize optional.

James Zhu made changes - 2022-10-04 05:19

Description

Original: This fix: [Fix default listSize by rob-ott - Pull Request #13 - jenkinsci/list-git-branches-parameter-plugin - GitHub|https://github.com/jenkinsci/list-git-branches-parameter-plugin/pull/13/files] Released as part of 0.0.11 breaks pipeline Jenkinsfile setup in 0.0.9 or earlier versions where the listSize parameter was not required. If you try to load a jenkinsfile using list-git-branches-parameter with no listSize parameter in a Jenkins with the 0.0.11 version of the plugin installed Jenkins will throw this error when creating pipeline: !image-2022-10-04-16-16-01-852.png! Conversely, if you try to load a pipeline Jenkinsfile using list-git-branches-parameter with a listSize parameter in Jenkins running 0.0.9 version of the plugin, Jenkins will also throw an error when creating pipeline:{{{}{}}} {code:java} 12:03:57 ERROR: (unknown source) No signature of method: listSize() is applicable for argument types: (java.lang.String) values: [5] 12:03:57 Possible solutions: name(), description(), remoteURL(), credentialsId(), defaultValue(), sortMode(), selectedValue(), quickFilterEnabled(), type(), tagFilter(), branchFilter() 12:03:57 Finished: FAILURE {code}   In organisation where pipeline files are version controlled and dynamically loaded into Jenkins to populate jobs it may be unavoidable to have jobs that want to call the plugin both ways due to Jenkins loading older jenkinsfile as part of a past release tag. Therefore ideally the plugin should handle both cases where listSize could be supplied or may be missing, possibly via overloading the method to make listSize optional.

New: This fix: [Fix default listSize by rob-ott - Pull Request #13 - jenkinsci/list-git-branches-parameter-plugin - GitHub|https://github.com/jenkinsci/list-git-branches-parameter-plugin/pull/13/files] Released as part of 0.0.11 breaks pipeline Jenkinsfile setup in 0.0.9 or earlier versions where the listSize parameter was not required. If you try to load a jenkinsfile using list-git-branches-parameter with no listSize parameter in a Jenkins with the 0.0.11 version of the plugin installed Jenkins will throw this error when creating pipeline: {code:java} ERROR: (unknown source) the following options are required and must be specified: listSize{code} Conversely, if you try to load a pipeline Jenkinsfile using list-git-branches-parameter with a listSize parameter in Jenkins running 0.0.9 version of the plugin, Jenkins will also throw an error when creating pipeline:{{{{}}{}}} {code:java} 12:03:57 ERROR: (unknown source) No signature of method: listSize() is applicable for argument types: (java.lang.String) values: [5] 12:03:57 Possible solutions: name(), description(), remoteURL(), credentialsId(), defaultValue(), sortMode(), selectedValue(), quickFilterEnabled(), type(), tagFilter(), branchFilter() 12:03:57 Finished: FAILURE {code}   In organisation where pipeline files are version controlled and dynamically loaded into Jenkins to populate jobs it may be unavoidable to have jobs that want to call the plugin both ways due to Jenkins loading older jenkinsfile as part of a past release tag. Therefore ideally the plugin should handle both cases where listSize could be supplied or may be missing, possibly via overloading the method to make listSize optional.

James Zhu made changes - 2022-10-04 05:20

Environment

Original: Jenkins Version: 2.303.1 List Git Branches Parameter Plugin Version: 0.0.11 Red Hat Enterprise Linux

New: Jenkins Version: 2.361.1 List Git Branches Parameter Plugin Version: 0.0.11 Red Hat Enterprise Linux

James Zhu made changes - 2022-10-04 05:23

Description

Original: This fix: [Fix default listSize by rob-ott - Pull Request #13 - jenkinsci/list-git-branches-parameter-plugin - GitHub|https://github.com/jenkinsci/list-git-branches-parameter-plugin/pull/13/files] Released as part of 0.0.11 breaks pipeline Jenkinsfile setup in 0.0.9 or earlier versions where the listSize parameter was not required. If you try to load a jenkinsfile using list-git-branches-parameter with no listSize parameter in a Jenkins with the 0.0.11 version of the plugin installed Jenkins will throw this error when creating pipeline: {code:java} ERROR: (unknown source) the following options are required and must be specified: listSize{code} Conversely, if you try to load a pipeline Jenkinsfile using list-git-branches-parameter with a listSize parameter in Jenkins running 0.0.9 version of the plugin, Jenkins will also throw an error when creating pipeline:{{{{}}{}}} {code:java} 12:03:57 ERROR: (unknown source) No signature of method: listSize() is applicable for argument types: (java.lang.String) values: [5] 12:03:57 Possible solutions: name(), description(), remoteURL(), credentialsId(), defaultValue(), sortMode(), selectedValue(), quickFilterEnabled(), type(), tagFilter(), branchFilter() 12:03:57 Finished: FAILURE {code}   In organisation where pipeline files are version controlled and dynamically loaded into Jenkins to populate jobs it may be unavoidable to have jobs that want to call the plugin both ways due to Jenkins loading older jenkinsfile as part of a past release tag. Therefore ideally the plugin should handle both cases where listSize could be supplied or may be missing, possibly via overloading the method to make listSize optional.

New: This fix: [Fix default listSize by rob-ott - Pull Request #13 - jenkinsci/list-git-branches-parameter-plugin - GitHub|https://github.com/jenkinsci/list-git-branches-parameter-plugin/pull/13/files] Released as part of 0.0.11 breaks pipeline Jenkinsfile setup in 0.0.9 or earlier versions where the listSize parameter was not required. If you try to load a jenkinsfile using list-git-branches-parameter with no listSize parameter in a Jenkins with the 0.0.11 version of the plugin installed Jenkins will throw this error when creating pipeline: {code:java} ERROR: (unknown source) the following options are required and must be specified: listSize{code} Conversely, if you try to load a pipeline Jenkinsfile using list-git-branches-parameter with a listSize parameter in Jenkins running 0.0.9 version of the plugin, Jenkins will also throw an error when creating pipeline: {code:java} 12:03:57 ERROR: (unknown source) No signature of method: listSize() is applicable for argument types: (java.lang.String) values: [5] 12:03:57 Possible solutions: name(), description(), remoteURL(), credentialsId(), defaultValue(), sortMode(), selectedValue(), quickFilterEnabled(), type(), tagFilter(), branchFilter() 12:03:57 Finished: FAILURE {code}   In organisation where pipeline files are version controlled and dynamically loaded into Jenkins to populate jobs it may be unavoidable to have jobs that want to call the plugin both ways due to Jenkins loading older jenkinsfile as part of a past release tag. Therefore ideally the plugin should handle both cases where listSize could be supplied or may be missing, possibly via overloading the method to make listSize optional.

James Zhu made changes - 2023-11-06 03:53

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

James Zhu made changes - 2023-11-06 03:54

Remote Link

New: This issue links to "pull request (Web Link)" [ 29017 ]