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

"Ignore target branch" no longer working

XMLWordPrintable

    • 2.5.3

      I have Ignore rebuilding merge branches when only the target branch changed option enabled but it does not seem to work when doing a repository scan.

         Checking pull request #126
Could not determine the mergability of pull request 126.  Retrying 4 more times...
      ‘Jenkinsfile’ found
    Met criteria
Changes detected: PR-126 (d4c1e76f93b3bd14801516c1492ba086104c9f40+f0f67d5327479b7265b99bcbbcc9dfba41ac9d74 (84faa76b0eb2e77205ecd1d76aad5db154d0043a) → d4c1e76f93b3bd14801516c1492ba086104c9f40+a5b83e33ac3c7e8f950da549835e9ff6b630ec19 (b5dcd562b082ef2d32f265da138488cabe1ab39f))
Scheduled build for branch: PR-126

    Checking pull request #125
Could not determine the mergability of pull request 125.  Retrying 4 more times...
      ‘Jenkinsfile’ found
    Met criteria
Changes detected: PR-125 (c58b5220b377015968b931d94e1687275b46c930+f0f67d5327479b7265b99bcbbcc9dfba41ac9d74 (d6aeb08d075198bd6cde73945584bdd77aa3dca0) → c58b5220b377015968b931d94e1687275b46c930+a5b83e33ac3c7e8f950da549835e9ff6b630ec19 (5377880b32efd962cf9efc0f9ef223f891a09a19))
Scheduled build for branch: PR-125

      I only ever see the Could not determine the mergability of pull request 125. Retrying 4 more times... line after a change has been merged to the target of some PRs and I rescan. When rescanning without any changes it's fine.

            bitwiseman Liam Newman
            awiddersheim Andrew Widdersheim
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: