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

Hard to see if branch was skipped because of discovery strategy

      I was recently trying to figure out why one of our branches got disabled and no longer built, not even looking at `Jenkinsfile` presence, and I followed a wrong trail for very long

      But in the end by chance found that the setup is to not process branches that also have PRs opened from them, and indeed someone made the PR

      So got two questions:

      1) I want a message telling why a branch was skipped! I sort of found where in github-branch-source-plugin code it begins "Checking branch" https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L987
      ... and where it decides it is no good https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/BranchDiscoveryTrait.java#L230
      ...but a lot of java voodoo happens in-between, so I have no idea where to plug in such logging that it would end up on the branch indexing console

      2) is there/can someone add some complex filter to always process branches from a certain name pattern (e.g. `release/*`), even if there are PRs from them?

          [JENKINS-74784] Hard to see if branch was skipped because of discovery strategy

          Nikolas Falco added a comment -

          This clone issue JENKINS-61290 for active github PR #318

          Nikolas Falco added a comment - This clone issue JENKINS-61290 for active github PR #318

          Nikolas Falco added a comment -

          This is how will look in the log scan

          Nikolas Falco added a comment - This is how will look in the log scan

            nfalco Nikolas Falco
            nfalco Nikolas Falco
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: