• Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • Jenkins 1.580.2
      Bitbucket build status notifier plugin 1.2.0

      This plugin works flawlessly, but it appears to only work if the `revision` string is interpreted as a string, and not evaluated (such as if a variable is provided)

      So if I use a specific revision (e.g. develop or tip), the build status is reported correctly.

      If I use a variable, however (such as with a build parameter), the build status is not posted correctly. In the job's console log, this message is posted: Sending build status INPROGRESS for commit $VERSION to BitBucket is done!. $VERSION is the variable that I'm using.

      In the system log, this message is posted:

      May 06, 2016 4:41:31 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier perform
      Bitbucket notify on finish
      May 06, 2016 4:41:31 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier notifyBuildStatus
      This response was received:{"error": {"message": "Changeset not found."}}
      May 06, 2016 4:41:31 PM INFO org.jenkinsci.plugins.bitbucket.BitbucketBuildStatusNotifier perform
      Bitbucket notify on finish succeeded
      

          [JENKINS-34651] Support for parameter in commit revision

          James Douglass created issue -

          Hi jdouglass, thanks for reporting this issue, I'll try to reproduce and fix the problem asap. I'll let you know, when it's fixed.

          Antonio Mansilla added a comment - Hi jdouglass , thanks for reporting this issue, I'll try to reproduce and fix the problem asap. I'll let you know, when it's fixed.
          Antonio Mansilla made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Hi again jdouglass, could you please provide more information about your scm and jenkins configuration? I need to be able to reproduce your problem first.

          Antonio Mansilla added a comment - Hi again jdouglass , could you please provide more information about your scm and jenkins configuration? I need to be able to reproduce your problem first.

          Sure thing!

          SCM: I'm using a mercurial repository hosted on bitbucket, cloned via https.
          Jenkins configuration: Jenkins version 1.580.2 (LTS)
          Jenkins plugins:

          Plugin Name Plugin Version
          ant 1.2
          antisamy-markup-formatter 1.1
          bitbucket 1.1.2
          bitbucket-build-status-notifier 1.2.0
          bitbucket-oauth 0.4
          build-timeout 1.14.1
          chucknorris 0.5
          cobertura 1.9.6
          copyartifact 1.33
          credentials 1.27
          cvs 2.11
          docker-plugin 0.10.2
          durable-task 1.5
          email-ext 2.39
          embeddable-build-status 1.7
          envinject 1.90
          external-monitor-job 1.2
          git 2.4.4
          git-client 1.19.6
          hipchat 0.1.9
          icon-shim 2.0.2
          javadoc 1.1
          jquery 1.7.2-1
          junit 1.0
          ldap 1.6
          mailer 1.17
          matrix-auth 1.1
          matrix-project 1.4
          maven-plugin 2.5
          mercurial 1.54
          multiple-scms 0.6
          nodelabelparameter 1.5.1
          oauth-credentials 0.3
          pam-auth 1.1
          parameterized-trigger 2.30
          publish-over-ssh 1.12
          rebuild 1.25
          scm-api 1.0
          script-security 1.13
          scripted-cloud-plugin 0.12
          shiningpanda 0.21
          slave-setup 1.8
          ssh-credentials 1.11
          ssh-slaves 1.8
          subversion 1.54
          swarm 1.22
          token-macro 1.11
          translation 1.10
          windows-slaves 1.1

          Happy to provide anything else ... just let me know what else would be helpful. Thanks!

          James Douglass added a comment - Sure thing! SCM: I'm using a mercurial repository hosted on bitbucket, cloned via https. Jenkins configuration: Jenkins version 1.580.2 (LTS) Jenkins plugins: Plugin Name Plugin Version ant 1.2 antisamy-markup-formatter 1.1 bitbucket 1.1.2 bitbucket-build-status-notifier 1.2.0 bitbucket-oauth 0.4 build-timeout 1.14.1 chucknorris 0.5 cobertura 1.9.6 copyartifact 1.33 credentials 1.27 cvs 2.11 docker-plugin 0.10.2 durable-task 1.5 email-ext 2.39 embeddable-build-status 1.7 envinject 1.90 external-monitor-job 1.2 git 2.4.4 git-client 1.19.6 hipchat 0.1.9 icon-shim 2.0.2 javadoc 1.1 jquery 1.7.2-1 junit 1.0 ldap 1.6 mailer 1.17 matrix-auth 1.1 matrix-project 1.4 maven-plugin 2.5 mercurial 1.54 multiple-scms 0.6 nodelabelparameter 1.5.1 oauth-credentials 0.3 pam-auth 1.1 parameterized-trigger 2.30 publish-over-ssh 1.12 rebuild 1.25 scm-api 1.0 script-security 1.13 scripted-cloud-plugin 0.12 shiningpanda 0.21 slave-setup 1.8 ssh-credentials 1.11 ssh-slaves 1.8 subversion 1.54 swarm 1.22 token-macro 1.11 translation 1.10 windows-slaves 1.1 Happy to provide anything else ... just let me know what else would be helpful. Thanks!
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 170821 ] New: JNJira + In-Review [ 185734 ]

            flagbit Antonio Mansilla
            jdouglass James Douglass
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: