Resolved images are cached even if <image> configuration changes between executions
See original GitHub issueWhen executing more than one goal with different values for the <image>
configuration, the first <image>
configuration is used to resolve images. The result is stored inside the plugin context. The next execution may potentially have a different configuration for <image>
, but won’t re-resolve images, but reuse the resolved images that have been stored in the plugin context. Hence it will operate on the wrong set of resolved images.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
cache reload does not appear to be working properly #10060
I see, so even if the Image ID changes, if the repo:tag is the same, ... list List all available images from the...
Read more >Best practices for speeding up builds - Google Cloud
You can specify the cached image by adding the --cache-from argument in your build config file, which will instruct Docker to build using...
Read more >Image Garbage Collection in OpenShift - Red Hat Hybrid Cloud
Images are kept indefinitely in the local cache, in particular an image is not deleted when there are no more containers using it...
Read more >How to avoid reinstalling packages when building Docker ...
Every time I build a new image, dependencies have to be reinstalled, which could be very slow in my region. One way I...
Read more >Caching Dependencies - CircleCI
This document is a guide to caching dependencies in CircleCI pipelines.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
👏 👌
I’m just about to remove the caching for the next release. It wasn’t such a good idea (also because of classloader issues I had lately).
That will be in the next release, which will probably released today.