• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • credentials-plugin
    • None
    • jenkins 2.133 Debian GNU/Linux 9 (stretch)
      credentials plugin 2.1.18
      Pipeline Multibranch plugin 2.20

      Setup:

      • multibranch pipeline based on subversion 1.8
      • after upgrading to credentials-plugin 2.1.18, my project is not scanned anymore, eventually displayed "NOT_BUILT". related log:
        Aug 20, 2018 7:45:00 AM jenkins.branch.MultiBranchProject$BranchIndexing run INFO: MY_MULTIBRANCH #20180820.074500 branch indexing action completed: NOT_BUILT in 47 ms Aug 20, 2018 7:45:00 AM hudson.model.Executor finish1 SEVERE: Executor threw an exception java.lang.LinkageError: com/cloudbees/plugins/credentials/domains/URIRequirementBuilder     at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:337)     at jenkins.scm.impl.subversion.SubversionSCMSource.retrieve(SubversionSCMSource.java:240)     at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:357)     at jenkins.scm.api.SCMSource.fetch(SCMSource.java:267)     at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:633)     at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:276)     at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:165)     at jenkins.branch.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1024)     at hudson.model.ResourceController.execute(ResourceController.java:97)     at hudson.model.Executor.run(Executor.java:429)
        
      • downgrading credentials plugin to 2.1.17 made it run/build again

          [JENKINS-53152] MultiBranch Pipeline repository scan broken

          Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

          Stephen Connolly added a comment - Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA

            Unassigned Unassigned
            kgiloo kgiloo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: