ExportXMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor
    • None
    • Environment:

      We generate about 900 multibranch jobs via the job DSL (as the result of a Gradle build).
      All jobs are regenerated, even if only a few are actually changed.

      We would normally see a full rescan of all repository branches
       and tags when regenerating job DSLs first time after a Jenkins
       version update. We use LTS releases, so this was fairly
       infrequent.

      But when updating Jenkins to LTS 2.568.1, we also got
      bitbucket-branch-source-plugin version 937.3.6. And after this,
       every job DSL regeneration causes a full scan of all
       repositories.

      I assumed it would be this plugin, but reverting just this plugin to version
      937.3.1 did not fix the observed behavior.

      Reverting the entire installation (to Jenkins LTS 2.555.2 and older plugins, among them bitbucket-branch-source-plugin version 937.3.1) did fortunately fix the problem.
      So I spent a long time trying to find a cause which was not this plugin.

      Eventually, I found that I could upgrade Jenkins and all other
       plugins, if I had first regenerated DSL jobs on the old release.

      Something in the 937.3.2 changes has an unfortunate side-effect on multibranch scan caching behavior.

      If anyone can figure out a reason and a fix from the above description, I will be happy to help test it.

      For now we are pinning bitbucket-branch-source-plugin to version 937.3.1.

      Thanks,
      Jesper Skov

            Assignee:
            Nikolas Falco
            Reporter:
            Jesper
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: