bbca430417
Stop compressing files that would otherwise be handled uncompressed in intermediate log handling. The reason for this is final log/artifact upload should decide if a file need to be compressed or not as some file hosting services (like swift) may not return the expected data if we get this wrong. This was noticed when we used swift to store intermediate tar.gz tarballs before final upload to permanent storage. When retrieving the tar.gz files from swift we got them back as uncompressed .tar files (because swift was being helpful) and then later when we try to uncompress these files we break. Instead we'll let the upload to swift (or other storage) decide if files should be compressed further than their existing state. This is the first change in the stack that updates this behavior for fetch-subunit-output. Change-Id: I5727b270d6d34c256fe78a443baa1ad6c3474108 |
||
|---|---|---|
| .. | ||
| subunit_tests | ||
| base.yaml | ||
| configure-mirrors.yaml | ||
| emit-job-header.yaml | ||
| ensure-output-dirs.yaml | ||
| fetch-output.yaml | ||
| fetch-subunit-output.yaml | ||
| fetch-zuul-cloner.yaml | ||
| prepare-workspace-git.yaml | ||
| validate-host.yaml | ||