-
Notifications
You must be signed in to change notification settings - Fork 2
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
Switch to build-module targets for e2e, uptest, render and yamllint and pull out project-specifc settings #54
Conversation
Test1:
|
Test2:
|
Test3:
|
Test4:
|
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.
Looks great but I am missing some form of embedded documentation on how to run uptest.
Also instead of Test{1,2,3,4}
it would be great to see the commands that were invoked for the testing , not only the output of the commands :)
Copy paste issue, let me correct :) |
…nd pull out project-specifc settings
46a637e
to
550b284
Compare
/test-examples |
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.
overall looks great, left couple of comments
0fde2bb
to
327aee4
Compare
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.
Just doc issues to fix, otherwise stuff works 👍
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.
Great reusable setup, thank you!
@ytsarev Thank you for the thorough review! |
Description of your changes
Switch to build-module provided targets for:
Also pulled out project-specific setting into
project.mk
which makes the Makefile fully generic.I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR, as appropriate.How has this code been tested
Manual verification by running described targets