-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
-
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).
- relates to
-
JENKINS-33169 Add different options for finding the reference build
- Open
-
JENKINS-22896 choose which job should be the reference build
- In Progress
-
JENKINS-33274 "Base build" link for first build of branch project
- Open
-
JENKINS-49079 Copy job properties for new branch project from base/default branch
- Open
-
JENKINS-47206 Guess at buckets for initial build via filesystem scan
- Resolved
- links to