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

TTP on PR will only initiate a single job

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Labels:
      None
    • Environment:
      2 jobs using the bitbucket PR builder on the same repo. Create a PR and add a "test this please" comment. Only one of the jobs will build.
    • Similar Issues:

      Description

      TTP (test this please) functionality only works for one job on a given repository. When a PR is created (or updated) all jobs that are configured with the Bitbucket Pull Request Builder will start. This does not happen for TTP comments. In this case, it looks like the first TTP initiates a job and adds a comment to the PR. This comment is enough to stop any subsequent jobs from executing (it thinks that the TTP has been satisfied). It does not seem to be using either the job name or the CI Identifier (which we set to be job name). The Stash Pull Request Builder does handle multiple jobs / TTP properly.

      also see - https://github.com/nishio-dens/bitbucket-pullrequest-builder-plugin/issues/82

        Attachments

          Activity

          Hide
          znerd Ernst de Haan added a comment -

          For me this is not the case. When I add a comment saying

          test this please

          …then all associated Jenkins jobs trigger (using the Bitbucket PR Builder plugin).

          My environment:

          • Bitbucket Cloud
          • Bitbucket PR Builder plugin 1.4.30
          • Jenkins 2.150.3

          Suggestion: either provide reproduction steps or mark this ticket as Resolved (not reproducible).

          Show
          znerd Ernst de Haan added a comment - For me this is not the case. When I add a comment saying test this please …then all associated Jenkins jobs trigger (using the Bitbucket PR Builder plugin). My environment: Bitbucket Cloud Bitbucket PR Builder plugin 1.4.30 Jenkins 2.150.3 Suggestion: either provide reproduction steps or mark this ticket as Resolved (not reproducible).

            People

            • Assignee:
              Unassigned
              Reporter:
              brianrepko Brian Repko
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: