Information about cached GHE remote pipelines that sourced from a Pull Request

Harness Experts
, , , ,
1

image
Information about cached GHE remote pipelines that sourced from a Pull Request

  • We show the last cached value on our end by default, irrespective of whatever happens on GIT for the given file.

  • The content is cached for each branch the file has been fetched for to date. The expiry time for content is 30 days. We don’t auto-reload cache on Back End as a synchronous job or similar.

  • Any execution of that particular pipeline or involving that particular template/input set updates the cached content as we fetch everything from GIT during execution.

  • Until any user-driven operation is performed, e.g. reload-from-git button on UI, execution of the pipeline / any entity via RUN button / UI or execution of entity via trigger etc., there’s no auto cache-refresh at the moment.

  • The “reload-from-git” option on three dots does the job We have the Reload from Git button to refresh the cache:

image
image1092×270 21.2 KB