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

Bitbucket notify on start failed: No change set to send to Bitbucket!

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      After setting up as described in the docs my build console output shows

      Bitbucket notify on start failed: No change set to send to Bitbucket!

      The bitbucket repository is not updated

        Attachments

          Activity

          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Antonio Mansilla
          Path:
          src/main/java/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier.java
          http://jenkins-ci.org/commit/bitbucket-build-status-notifier-plugin/9a8ca27818d7c2b074a63dfb40914deb8825711e
          Log:
          [Fix JENKINS-32519] Fix problem finding current revision

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Antonio Mansilla Path: src/main/java/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifier.java http://jenkins-ci.org/commit/bitbucket-build-status-notifier-plugin/9a8ca27818d7c2b074a63dfb40914deb8825711e Log: [Fix JENKINS-32519] Fix problem finding current revision
          Hide
          flagbit Antonio Mansilla added a comment -

          jake bishop So finally I got the problem solved and changes got merged into master. It will be released next week or maybe sooner.

          Show
          flagbit Antonio Mansilla added a comment - jake bishop So finally I got the problem solved and changes got merged into master. It will be released next week or maybe sooner.
          Hide
          flagbit Antonio Mansilla added a comment -

          jake bishop Last friday was released the version that fix this problem.

          Please install the new version and try again if the problem is fixed.

          Show
          flagbit Antonio Mansilla added a comment - jake bishop Last friday was released the version that fix this problem. Please install the new version and try again if the problem is fixed.
          Hide
          yakobe jake bishop added a comment -

          The new build seems to work. We get messages like the following in our console log:

          Sending build status INPROGRESS for commit 58c508d68d96ea6a237f90c4c599ade5849364c7 to BitBucket is done!
          

          However, it still doesn't appear all the time in bitbucket. It seems this particularly noticable for pull requests. I remember you mentioned some issue with Forked repo's, but we are not working with forks. Any ideas?

          Show
          yakobe jake bishop added a comment - The new build seems to work. We get messages like the following in our console log: Sending build status INPROGRESS for commit 58c508d68d96ea6a237f90c4c599ade5849364c7 to BitBucket is done! However, it still doesn't appear all the time in bitbucket. It seems this particularly noticable for pull requests. I remember you mentioned some issue with Forked repo's, but we are not working with forks. Any ideas?
          Hide
          flagbit Antonio Mansilla added a comment -

          jake bishop That's fine. If the status doesn't appear in bitbucket is because it seems to not be supported by Bitbucket, I already created an issue at Bitbucket with following response:

          I've checked with our Developers and build status simply isn't supported on PRs from repo forks right now. This is the reason you are not seeing the status on the PR. However, that should works fine if you are not working with forks.
          Please let us know if there's anything else we can do for you.

          All the best,
          Renato Rudnicki
          Atlassian Support

          I'll resolve this issue since the problem was solved. If anyone face new problems with this, please create a new issue.

          Show
          flagbit Antonio Mansilla added a comment - jake bishop That's fine. If the status doesn't appear in bitbucket is because it seems to not be supported by Bitbucket, I already created an issue at Bitbucket with following response: I've checked with our Developers and build status simply isn't supported on PRs from repo forks right now. This is the reason you are not seeing the status on the PR. However, that should works fine if you are not working with forks. Please let us know if there's anything else we can do for you. All the best, Renato Rudnicki Atlassian Support I'll resolve this issue since the problem was solved. If anyone face new problems with this, please create a new issue.

            People

            • Assignee:
              flagbit Antonio Mansilla
              Reporter:
              yakobe jake bishop
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: