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

Make number of retries configurable when waiting for GitHub merge commit

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      Jenkins 2.249.2
      github-branch-source-plugin 2.8.2
    • Similar Issues:

      Description

      We are experiencing some times, that after a GitHub PR is created, the corresponding Jenkins CI is not started (using GitHub Organization Folder).

      In such a case we see this in the multibranch event log:

          Checking pull request #2742
      Waiting for GitHub to create a merge commit for pull request 2742.  Retrying 4 more times...
      Waiting for GitHub to create a merge commit for pull request 2742.  Retrying 3 more times...
      Waiting for GitHub to create a merge commit for pull request 2742.  Retrying 2 more times...
            ‘Jenkinsfile’ not found
          Does not meet criteria
      
      

      We assume that if Jenkins would wait a little bit longer or retry some more times, it would get the merge commit and the job would start. Because if we redeliver the GitHub event for the PR creation, the build is scheduled.

      So we would like to have the[ sleep time and/or number of retries|https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L1687] be made configurable.

       

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            dschey Jürgen Wakunda
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: