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

Bitbucket Branch Source Plugin: changes are missing for builds

    XMLWordPrintable

Details

    Description

      Changes always empty for builds. In log console I see:
      WARN: Revision data for previous build unavailable; unable to determine change log

      Attachments

        1. Selection_001.png
          Selection_001.png
          40 kB
        2. Selection_002.png
          Selection_002.png
          33 kB
        3. Selection_003.png
          Selection_003.png
          173 kB

        Issue Links

          Activity

            This is blocks developers, because they don't see wich changes builds and fail builds.

            argus_k Dmytro Kozlovskyi added a comment - This is blocks developers, because they don't see wich changes builds and fail builds.
            jamesdumay James Dumay added a comment -

            argus_k keep an eye out for version 2.2 hitting the update centre. I suspect some strange things like this are solved in that release (its more inline with the Github plugin)

            jamesdumay James Dumay added a comment - argus_k keep an eye out for version 2.2 hitting the update centre. I suspect some strange things like this are solved in that release (its more inline with the Github plugin)

            jamesdumay yes, looks like fixed in 2.2. Thanks.

            argus_k Dmytro Kozlovskyi added a comment - jamesdumay  yes, looks like fixed in 2.2. Thanks.
            jamesdumay James Dumay added a comment -

            argus_k thats great to hear.

            jamesdumay James Dumay added a comment - argus_k thats great to hear.

            Hi, jamesdumay . This issue back again after release  Bitbucket Branch Source Plugin 2.2.6. It works in 2.2.5 but not in 2.2.6+. Should I reopen this ticket or create a new one? Thanks.

            argus_k Dmytro Kozlovskyi added a comment - Hi, jamesdumay . This issue back again after release  Bitbucket Branch Source Plugin 2.2.6. It works in 2.2.5 but not in 2.2.6+. Should I reopen this ticket or create a new one? Thanks.

            People

              amuniz Antonio Muñiz
              argus_k Dmytro Kozlovskyi
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: