Do not use cache in github image build action#15308
Merged
Merged
Conversation
Member
Author
|
Showing some testing: |
Member
Author
|
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. |
TheRealHaoLiu
approved these changes
Jun 28, 2024
chrismeyersfsu
approved these changes
Jun 28, 2024
Member
Author
|
Confirming from check output that this does not undo the cache for checks: |
Member
Author
|
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. |
Member
Author
djyasin
pushed a commit
to djyasin/awx
that referenced
this pull request
Sep 16, 2024
* Do not use cache in actual image build action * Add cache args to kube prod builds
djyasin
pushed a commit
to djyasin/awx
that referenced
this pull request
Nov 11, 2024
* Do not use cache in actual image build action * Add cache args to kube prod builds
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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-fromor we use--no-cache. It is hard to do this inmakelanguage. This is my best shot.ISSUE TYPE
COMPONENT NAME