-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[build] Check if patches are applied before applying patches #13386
Conversation
Maybe just need to fix a cleanup stage for some packages? I mean usually we have the next steps:
Some packages like ntp have incorrect 1st step: So if directory with source code is removed correctly we don't have any issues with applying patches when we rerun make. But it's just a suggestion. |
That will be a big change. This small change will work in a lot of scenarios. |
…et#13386) Why I did it If make fails, we can't rerun the make process, because existing patches can't apply again. How I did it Check if patches are applied. if yes, don't apply patches again. How to verify it
Cherry-pick PR to 202205: #13435 |
…#13435) Why I did it If make fails, we can't rerun the make process, because existing patches can't apply again. How I did it Check if patches are applied. if yes, don't apply patches again. How to verify it Co-authored-by: Liu Shilong <[email protected]>
…et#13386) Why I did it If make fails, we can't rerun the make process, because existing patches can't apply again. How I did it Check if patches are applied. if yes, don't apply patches again. How to verify it
Cherry-pick PR to 202106: #13598 |
Cherry-pick PR to 202111: #13599 |
Why I did it If make fails, we can't rerun the make process, because existing patches can't apply again. How I did it Check if patches are applied. if yes, don't apply patches again. How to verify it
Why I did it If make fails, we can't rerun the make process, because existing patches can't apply again. How I did it Check if patches are applied. if yes, don't apply patches again. How to verify it
…et#13386) Why I did it If make fails, we can't rerun the make process, because existing patches can't apply again. How I did it Check if patches are applied. if yes, don't apply patches again. How to verify it
Cherry-pick PR to 202211: #13656 |
Why I did it If make fails, we can't rerun the make process, because existing patches can't apply again. How I did it Check if patches are applied. if yes, don't apply patches again. How to verify it
Why I did it If make fails, we can't rerun the make process, because existing patches can't apply again. #13386 missed some change.
…net#13566) Why I did it If make fails, we can't rerun the make process, because existing patches can't apply again. sonic-net#13386 missed some change.
Why I did it
If make fails, we can't rerun the make process, because existing patches can't apply again.
How I did it
Check if patches are applied. if yes, don't apply patches again.
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)