Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63374

Bitbucket plugin changed API for the bitbucketPush trigger in an incompatible way

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Component/s: bitbucket-plugin
    • Labels:
      None
    • Environment:
      Jenkins 2.235.3
      Bitbucket plugin 1.1.19
    • Similar Issues:
    • Released As:
      1.1.21

      Description

      After I updated Bitbucket plugin from 1.1.18 to 1.1.19 our builds ceased to work with the following message:
       
      "bitbucketPush" should have 1 arguments but has 0 arguments instead.
       
      Rolling back to 1.1.18 fixed the issue

        Attachments

          Activity

          Hide
          vlazdra Vladimir Zdravkovic added a comment -

          Experiencing the same issue. There is nothing mentioned in the changelog of the bitbucket-plugin anywhere.

          Show
          vlazdra Vladimir Zdravkovic added a comment - Experiencing the same issue. There is nothing mentioned in the changelog of the bitbucket-plugin anywhere.
          Hide
          basith Abdul Basith S added a comment -

          Yes, its a breaking change, so had to rollback (downgrade) the Plugin version.

          Show
          basith Abdul Basith S added a comment - Yes, its a breaking change, so had to rollback (downgrade) the Plugin version.
          Hide
          tzach_solomon Tzach Solomon added a comment - - edited

          Gottfried Ganßauge sorry for this. The change was done in order to support the multiple cases that were opened about the matching URL. The override solution addressed in a generic way.

          Can you please help me with reproducing this issue?

          Show
          tzach_solomon Tzach Solomon added a comment - - edited Gottfried Ganßauge sorry for this. The change was done in order to support the multiple cases that were opened about the matching URL. The override solution addressed in a generic way. Can you please help me with reproducing this issue?
          Hide
          ganssauge Gottfried Ganßauge added a comment -

          I'd really like to - but I don't see how.
          Our usage of the feature is pretty basic:
          We have lots of pipelines like this:

          pipeline {
              // options, ...
          
              triggers {
                  upstream(threshold: hudson.model.Result.SUCCESS, upstreamProjects: upstreamProjects)
                  bitbucketPush()
              }
          
             // pipeline steps following ...
          }
          

          Those ceased to work with the new release with the message mentioned in the report.

          So what can I do?

          Show
          ganssauge Gottfried Ganßauge added a comment - I'd really like to - but I don't see how. Our usage of the feature is pretty basic: We have lots of pipelines like this: pipeline { // options, ... triggers { upstream(threshold: hudson.model.Result.SUCCESS, upstreamProjects: upstreamProjects) bitbucketPush() } // pipeline steps following ... } Those ceased to work with the new release with the message mentioned in the report. So what can I do?
          Hide
          axie Andy Xie added a comment -

          Also experiencing the same thing. Had to downgrade back to 1.1.18. I simply have the bitbucketPush() in my triggers and that was enough to reproduce it.

          Show
          axie Andy Xie added a comment - Also experiencing the same thing. Had to downgrade back to 1.1.18. I simply have the bitbucketPush() in my triggers and that was enough to reproduce it.
          Hide
          bobf Bob Farrell added a comment - - edited

          Tzach Solomon This Jenkinsfile recreates the error:

          pipeline {
            triggers {
              bitbucketPush()
            }
          
            agent {
              docker {
                image 'ubuntu'
              }
            }
          
            stages {
              stage('Example') {
                steps {
                  sh 'echo "Example"'
                }
              }
            }
          }
          

           

          Show
          bobf Bob Farrell added a comment - - edited Tzach Solomon This Jenkinsfile recreates the error: pipeline { triggers { bitbucketPush() } agent { docker { image 'ubuntu' } } stages { stage( 'Example' ) { steps { sh 'echo "Example" ' } } } }  
          Hide
          tzach_solomon Tzach Solomon added a comment -

          Reverted back to empty constructor and changed to use @DataBoundSetter.
          Should be fixed in 1.1.21

          Show
          tzach_solomon Tzach Solomon added a comment - Reverted back to empty constructor and changed to use @DataBoundSetter. Should be fixed in 1.1.21
          Hide
          tzach_solomon Tzach Solomon added a comment -

          Gottfried Ganßauge thanks for reporting the problem and thanks all for the reproduction scenarios
          I was able to reproduce the problem and I think I fixed it, see version 1.1.21

          Show
          tzach_solomon Tzach Solomon added a comment - Gottfried Ganßauge thanks for reporting the problem and thanks all for the reproduction scenarios I was able to reproduce the problem and I think I fixed it, see version 1.1.21
          Hide
          ganssauge Gottfried Ganßauge added a comment -

          Thanks, Tzach Solomon - for me it works again with 1.21.

          Show
          ganssauge Gottfried Ganßauge added a comment - Thanks, Tzach Solomon - for me it works again with 1.21.
          Hide
          tzach_solomon Tzach Solomon added a comment -

          Fixed

          Show
          tzach_solomon Tzach Solomon added a comment - Fixed

            People

            Assignee:
            tzach_solomon Tzach Solomon
            Reporter:
            ganssauge Gottfried Ganßauge
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: