-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not use cache in github image build action #15308
Conversation
Showing some testing:
|
I merged stuff today, for a fact, and it ran the job to build the image for a fact.
Yet I still see:
It definitely ran the command to push the image. The problem is that the image it pushes has the same hash as the image before. So no change, that's why my image shows it modified 25 hours ago. |
Confirming from check output that this does not undo the cache for checks:
|
Now I'm closely watching the post-merge action: https://github.com/ansible/awx/actions/runs/9713929243/job/26811829563
That line initially makes it look like it's working. |
* Do not use cache in actual image build action * Add cache args to kube prod builds
* Do not use cache in actual image build action * Add cache args to kube prod builds
SUMMARY
I create this due to struggling with the action:
https://github.com/ansible/awx/actions/workflows/devel_images.yml
It will not pick up a new DAB version.
When it does this, it produces an image that uses a DAB git hash 3 commits behind the latest. Clearly, because it never installed requirements. You frequently see these timings:
It's probable that requirements were not installed if it took less than 1 minute.
I don't want to re-install requirements on ever PR, which creates the central challenge here.
Either we use
--cache-from
or we use--no-cache
. It is hard to do this inmake
language. This is my best shot.ISSUE TYPE
COMPONENT NAME