Log ETag of extracted cache archive if available
What does this MR do?
This commit adds the ETag from the downloaded cache file to the "Downloading cache" message in the job.
When debugging CI jobs, we found that it would be useful to log the ETag of the extracted cache file. The ETag header is supported by Amazon S3, Google Cloud Storage, and Azure.
Why was this MR needed?
It would help with debugging CI jobs.
What's the best way to test this MR?
- Configure the runner cache with object storage. I used Azure Blob Storage.
- Create a CI job that saves a cache file:
image: ruby:latest
test:
stage: test
script:
- date
- echo "hello" > test.txt
cache:
paths:
- test.txt
artifacts:
paths:
- test.txt
- Run a CI job:
What are the relevant issue numbers?
Relates to gitlab#460139 (closed)
Edited by Stan Hu