mirror of
				https://gitea.com/actions/cache.git
				synced 2025-10-31 07:47:07 +00:00 
			
		
		
		
	Compare commits
	
		
			9 Commits
		
	
	
		
			v3.0.11
			...
			bishal-pdM
		
	
	| Author | SHA1 | Date | |
|---|---|---|---|
|   | be52f75d6f | ||
|   | 8bec1e4cc3 | ||
|   | 14f2d18ea2 | ||
|   | 083fb3041b | ||
|   | 5085ac92ef | ||
|   | 76639bb4e5 | ||
|   | 5294b3f306 | ||
|   | 4fe9c4bd54 | ||
|   | 2b04a41915 | 
							
								
								
									
										32
									
								
								.github/pull_request_template.md
									
									
									
									
										vendored
									
									
										Normal file
									
								
							
							
						
						
									
										32
									
								
								.github/pull_request_template.md
									
									
									
									
										vendored
									
									
										Normal file
									
								
							| @@ -0,0 +1,32 @@ | ||||
| <!--- Provide a general summary of your changes in the Title above --> | ||||
|  | ||||
| ## Description | ||||
| <!--- Describe your changes in detail --> | ||||
|  | ||||
| ## Motivation and Context | ||||
| <!--- Why is this change required? What problem does it solve? --> | ||||
| <!--- If it fixes an open issue, please link to the issue here. --> | ||||
|  | ||||
| ## How Has This Been Tested? | ||||
| <!--- Please describe in detail how you tested your changes. --> | ||||
| <!--- Include details of your testing environment, and the tests you ran to --> | ||||
| <!--- see how your change affects other areas of the code, etc. --> | ||||
|  | ||||
| ## Screenshots (if appropriate): | ||||
|  | ||||
| ## Types of changes | ||||
| <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> | ||||
| - [ ] Bug fix (non-breaking change which fixes an issue) | ||||
| - [ ] New feature (non-breaking change which adds functionality) | ||||
| - [ ] Breaking change (fix or feature that would cause existing functionality to change) | ||||
| - [ ] Documentation (add or update README or docs) | ||||
|  | ||||
| ## Checklist: | ||||
| <!--- Go over all the following points, and put an `x` in all the boxes that apply. --> | ||||
| <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! --> | ||||
| - [ ] My code follows the code style of this project. | ||||
| - [ ] My change requires a change to the documentation. | ||||
| - [ ] I have updated the documentation accordingly. | ||||
| - [ ] I have read the **CONTRIBUTING** document. | ||||
| - [ ] I have added tests to cover my changes. | ||||
| - [ ] All new and existing tests passed. | ||||
							
								
								
									
										4
									
								
								.github/workflows/workflow.yml
									
									
									
									
										vendored
									
									
								
							
							
						
						
									
										4
									
								
								.github/workflows/workflow.yml
									
									
									
									
										vendored
									
									
								
							| @@ -99,7 +99,7 @@ jobs: | ||||
|       options: --dns 127.0.0.1 | ||||
|     services: | ||||
|       squid-proxy: | ||||
|         image: datadog/squid:latest | ||||
|         image: ubuntu/squid:latest | ||||
|         ports: | ||||
|           - 3128:3128 | ||||
|     env: | ||||
| @@ -122,7 +122,7 @@ jobs: | ||||
|       options: --dns 127.0.0.1 | ||||
|     services: | ||||
|       squid-proxy: | ||||
|         image: datadog/squid:latest | ||||
|         image: ubuntu/squid:latest | ||||
|         ports: | ||||
|           - 3128:3128 | ||||
|     env: | ||||
|   | ||||
							
								
								
									
										15
									
								
								README.md
									
									
									
									
									
								
							
							
						
						
									
										15
									
								
								README.md
									
									
									
									
									
								
							| @@ -19,7 +19,7 @@ See ["Caching dependencies to speed up workflows"](https://docs.github.com/en/ac | ||||
| * Fixed cache not working with github workspace directory or current directory. | ||||
| * Fixed the download stuck problem by introducing a timeout of 1 hour for cache downloads. | ||||
| * Fix zstd not working for windows on gnu tar in issues. | ||||
| * Allowing users to provide a custom timeout as input for aborting download of a cache segment using an environment variable `SEGMENT_DOWNLOAD_TIMEOUT_MIN`. Default is 60 minutes. | ||||
| * Allowing users to provide a custom timeout as input for aborting download of a cache segment using an environment variable `SEGMENT_DOWNLOAD_TIMEOUT_MINS`. Default is 60 minutes. | ||||
|  | ||||
| Refer [here](https://github.com/actions/cache/blob/v2/README.md) for previous versions | ||||
|  | ||||
| @@ -34,17 +34,18 @@ If you are using this inside a container, a POSIX-compliant `tar` needs to be in | ||||
|  | ||||
| * `path` - A list of files, directories, and wildcard patterns to cache and restore. See [`@actions/glob`](https://github.com/actions/toolkit/tree/main/packages/glob) for supported patterns. | ||||
| * `key` - An explicit key for restoring and saving the cache | ||||
| * `restore-keys` - An ordered list of prefix-matched keys to use for restoring stale cache if no cache hit occurred for key. Note | ||||
| `cache-hit` returns false in this case. | ||||
| * `restore-keys` - An ordered list of prefix-matched keys to use for restoring stale cache if no cache hit occurred for key. | ||||
|  | ||||
| #### Environment Variables | ||||
| * `SEGMENT_DOWNLOAD_TIMEOUT_MIN` - Segment download timeout (in minutes, default `60`) to abort download of the segment if not completed in the defined number of minutes. [Read more](#cache-segment-restore-timeout) | ||||
| * `SEGMENT_DOWNLOAD_TIMEOUT_MINS` - Segment download timeout (in minutes, default `60`) to abort download of the segment if not completed in the defined number of minutes. [Read more](#cache-segment-restore-timeout) | ||||
|  | ||||
| ### Outputs | ||||
|  | ||||
| * `cache-hit` - A boolean value to indicate an exact match was found for the key | ||||
| * `cache-hit` - A boolean value to indicate an exact match was found for the key.  | ||||
|  | ||||
| > See [Skipping steps based on cache-hit](#Skipping-steps-based-on-cache-hit) for info on using this output | ||||
| > Note: `cache-hit` will be set to `true` only when cache hit occurs for the exact `key` match. For a partial key match via `restore-keys` or a cache miss, it will be set to `false`. | ||||
|  | ||||
| See [Skipping steps based on cache-hit](#skipping-steps-based-on-cache-hit) for info on using this output | ||||
|  | ||||
| ### Cache scopes | ||||
| The cache is scoped to the key and branch. The default branch cache is available to other branches. | ||||
| @@ -152,7 +153,7 @@ A repository can have up to 10GB of caches. Once the 10GB limit is reached, olde | ||||
|  | ||||
| ## Skipping steps based on cache-hit | ||||
|  | ||||
| Using the `cache-hit` output, subsequent steps (such as install or build) can be skipped when a cache hit occurs on the key. | ||||
| Using the `cache-hit` output, subsequent steps (such as install or build) can be skipped when a cache hit occurs on the key.  It is recommended to install the missing/updated dependencies in case of a partial key match when the key is dependent on the `hash` of the package file. | ||||
|  | ||||
| Example: | ||||
| ```yaml | ||||
|   | ||||
| @@ -28,7 +28,7 @@ | ||||
|  | ||||
| ### 3.0.8 | ||||
| - Fix zstd not working for windows on gnu tar in issues [#888](https://github.com/actions/cache/issues/888) and [#891](https://github.com/actions/cache/issues/891). | ||||
| - Allowing users to provide a custom timeout as input for aborting download of a cache segment using an environment variable `SEGMENT_DOWNLOAD_TIMEOUT_MIN`. Default is 60 minutes. | ||||
| - Allowing users to provide a custom timeout as input for aborting download of a cache segment using an environment variable `SEGMENT_DOWNLOAD_TIMEOUT_MINS`. Default is 60 minutes. | ||||
|  | ||||
| ### 3.0.9 | ||||
| - Enhanced the warning message for cache unavailablity in case of GHES. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user