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

Github PR Unwanted Check run after base branch got a new commit

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When a PR webhook register a new event, it would check scm combination of the base branch and compare branch. If the combination is different from what is prior, it would trigger a run for a multibranch pipeline with such PR.

      Changes detected: PR-11911 (83e83c004a14abd5bc4f87fa9c09d564c54cc1d7+d80c0362c99f616e24a1a45662c179e8868453a1 (71d0d7999f35d972e227b201d2d29e619555a213) → 83e83c004a14abd5bc4f87fa9c09d564c54cc1d7+2d56644a7be0811bbb2b50825feb89065718be7d (e35d7ab0ced2c43f8b48a6bac294fa6d373aa18d))
      

      Thus it means that, if the base branch get a new commit (from another PR merge like the example above), then the next webhook event would trigger another run. This leads to confusing rerun of PR checks, as the webhook event may get triggered by a PR title change or a PR comment.

      Would it be possible to configure the webhook somehow to ignore PR title change or PR comments for a certain Jenkins multibranch pipeline job ?

      Note: The auto manage webhook option is system wide and is needed for other pipeline jobs in our use case.

        Attachments

          Activity

          Hide
          bitwiseman Liam Newman added a comment -

          If you switch your PR strategy to using the source branch instead of merging with the base branch, there will not be a change detected when the base branch changes.

          Show
          bitwiseman Liam Newman added a comment - If you switch your PR strategy to using the source branch instead of merging with the base branch, there will not be a change detected when the base branch changes.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            cuong_you Cuong
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: