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

Use primary job as fallback when searching for test records

    • 380.vc9145a_5f849f

      Currently, test results are only taken from the last builds of this job. The result is that the first build(s) of a newly created branch (when using multi-branch jobs) do not run tests in parallel, unless the build for this branch is non-FAILURE. With short-lived feature branches, this results in unsatisfying long build times.

      In case of multi-branch jobs, other branches could act as a source for test records as well. The question, which branch to use as reference can be answered with the SCM's help - the PrimaryInstanceMetadataAction is assigned by several SCM plugins and denotes one/multiple branches as "primary" (in Git: the default branch when checking out).

          [JENKINS-46028] Use primary job as fallback when searching for test records

          Steffen Gebert added a comment - Pull request:  https://github.com/jenkinsci/parallel-test-executor-plugin/pull/26

          Jesse Glick added a comment -

          Note: implemented using a somewhat different API that more precisely identifies the base branch for a “pull request” or whatever the branch source calls it. Does not refer to a “default branch” in the general case of running the first build of some arbitrary branch project.

          Jesse Glick added a comment - Note: implemented using a somewhat different API that more precisely identifies the base branch for a “pull request” or whatever the branch source calls it. Does not refer to a “default branch” in the general case of running the first build of some arbitrary branch project.

            vlatombe Vincent Latombe
            stephenking Steffen Gebert
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: