68d7a99cee
With job parents that supply data we might end up updating the (secret) parent data and artifacts of a job multiple times in addition to also storing duplicate data as most of this information is part of the parent's build result. Instead we will collect the parent data and artifacts before scheduling a build request and send it as part of the request paramters. If those parameters are part of the build request the executor will use them, otherwise it falls back on using the data from the job for backward compatibility. This change affects the behavior of job deduplication in that input data from parent jobs is no longer considered when deciding if a job can be deduplicated or not. Change-Id: Ic4a85a57983d38f033cf63947a3b276c1ecc70dc
6 lines
152 B
YAML
6 lines
152 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Input data from a parent job (return data or artifacts) no longer
|
|
influences whether a child job can be deduplicated or not.
|