We ran into a situation where auth was failing to pull from a private registry. We already had pulled the image previsouly so it was cached. We had
pull: true set.
We pushed an updated version of a tag to our registry. Drone was not pulling it due to auth failure, which I would expect. But the auth failure was not in logs and Drone continued to run tests from the cached image, which I would not expect. So we thought Drone was ignoring
pull: true for some reason. We later “updated” our registry auth (we remember it had changed) in Drone and everything started to work as expected.
- registry credentials are provided
- Drone is not able to auth
pull: trueis set
I would expect Drone to fail, even if it had previously downloaded the image.
Just wondering if expectation I have makes sense or if there is a reason for the way it behaves now. If it seems like a valid expectation I don’t mind creating an issue to track it.