Ability to turn off upload for the Harness cache
complete
C
Concerned Rabbit
User need the ability to use the cache on a stage but only upload in 1. This will allow us to save 1 minute in total execution time, and many more minutes in execution minutes.
Turning off only the uploading of cache on a per stage basis would solve the issue for them.
Log In
Canny AI
Merged in a post:
Option to skip file upload step in pipeline
R
Rubber Scallop
I noticed that once the upload step starts, there is no option to skip it if the user does not have or want any file to upload. It would be beneficial to have an option to skip this step to streamline the process when file uploads are unnecessary.
N
Nofar Bluestein
complete
This post was marked as
in progress
N
Nofar Bluestein
complete
N
Nofar Bluestein
Hey, this is already available with Cache intelligence.
If you navigate the stage overview , under cache intelligence there are additional (optional) settings you can set and you'll find the ability to set cache policy (pull, push or both) there.
Please see screen shot attached.
Regards,
Nofar Bluestein
CI product team
N
Nofar Bluestein
Merged in a post:
When "Save cache to Harness" step fails, execution status is set to IGNOREFAILED instead of SUCCESS
C
Concerned Rabbit
We have 3 stages that leverage the same cached data. The way Harness' cache intelligence works was causing all 3 stages to spend time uploading the same cache back at the end of the job. So we added a "Run" command to all stages but one of them, and deleted the cache directories so we wouldn't incur in this extra cost to upload the same cache multiple times (our pipeline runs with many many parallel stages, so this is a significant amount of wasted minutes).
However, since the directory is missing, the "Save Cache to Harness" step fails, but it's a failure that gets ignored, so our builds are not blocked. However, this skews reporting for us, because the execution state for all our builds is now set as IGNOREFAILED, instead of SUCCESS.
See the attached dashboard screenshot to understand why this is relevant.
The solution to our case would be to allow us to use the harness cache in read only mode, meaning the stage would read and use the cache, but not upload it back.
Pranav Rastogi
long-term