I have a couple of tools I've created Docker images for. These tools need a license to run, which they contact a floating license server on our network to check for available seats and take hold of a license for it's run. I'm not clear how this would work with the caching feature of Dagger. As that command is generally at the start of a Dagger pipeline, it won't change so does Dagger just take the cached result for this license check command, or does it run every time, to be sure we get the latest license status and availability?
#Dagger and Tool License Available Check
toxic furnace
safe marsh
I have a couple of tools I've created Docker images for. These tools need a lice...
It should used the cached result unless you use the "cachebuster" pattern but this will a negative impact o the rest of your pipeline.
Are you able to do the license check last?
toxic furnace
Thanks for the response, that's useful to know. Possibly I should be able to move it down the order of commands. I'll have a look
strong pewter
if the check command doesn't randomly change the inputs of the other commands (eg if it doesn't write a random file to the filesystem) then it won't affect the caching of subsequent commands
so it should be fine running it with a cachebuster as early as you'd like (again if it doesn't mess with the container)