-
Notifications
You must be signed in to change notification settings - Fork 11
Added filters to rebuild only the changed images #59
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
base: mainline
Are you sure you want to change the base?
Conversation
Signed-off-by: Hanxi Zhang <[email protected]>
Signed-off-by: Hanxi Zhang <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments. I am interested in how we are testing this. Let's add some workflows and tests through maybe personal forks.
Signed-off-by: Hanxi Zhang <[email protected]>
Signed-off-by: Hanxi Zhang <[email protected]>
Signed-off-by: Hanxi Zhang <[email protected]>
f484e61
to
0486e06
Compare
Signed-off-by: Hanxi Zhang <[email protected]>
Signed-off-by: Hanxi Zhang <[email protected]>
…ker files Signed-off-by: Hanxi Zhang <[email protected]>
Signed-off-by: Hanxi Zhang <[email protected]>
Signed-off-by: Hanxi Zhang <[email protected]>
Signed-off-by: Hanxi Zhang <[email protected]>
Signed-off-by: Hanxi Zhang <[email protected]>
Signed-off-by: Hanxi Zhang <[email protected]>
… mainline Signed-off-by: Hanxi Zhang <[email protected]>
…n when make a PR or push to mainline Signed-off-by: Hanxi Zhang <[email protected]>
…o job to run for push to mainline Signed-off-by: Hanxi Zhang <[email protected]>
Signed-off-by: Hanxi Zhang <[email protected]>
Hi @sarthakaggarwal97, here are the screenshots showing how I tested the changes. I’ve also linked the PR from my personal fork. Expected BehaviorThe expected behavior is as follows: when pushing to the mainline branch, only the version whose Dockerfile has been modified should be built. If no Dockerfile is changed, no image should be built. For pushes to other branches or for pull requests, all jobs should run. Only modified 8.1 dockerfile: hanxizh9910#20PR:![]() Push to mainline:![]() Modified both 8.1 and 9.0:hanxizh9910#21PR:![]() Push to mainline:![]() Modified the ci.yml(not a dockerfile):hanxizh9910#22PR:![]() Push to mainline:![]() |
Signed-off-by: Sarthak Aggarwal <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks @hanxizh9910 for taking this up and testing it. @roshkhatri and @Nikhil-Manglore please take a look. It'll be good to have this for 9.0 GA.
Problem
When releasing new changes, all Docker images are rebuilt even when only one version changes. This wastes significant time and resources.
Solution
This PR adds change detection to the CI workflow and detect which version folder changed.
Testing
Verified the optimization works for: