-
Notifications
You must be signed in to change notification settings - Fork 61
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
Separate e2e tests and KIND from main Makefile #255
Conversation
This is a preparation step on the way to extract E2E-related code into it's own Makefile, if possible.
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.
I would propose to introduce lower-case variables for "make internal" variables, not necessary intended to be edited by developers (e.g. $(KIND_BIN)
to $(kind_bin)
. Additionally, I'd propose to create a Makevariables.mk
file, to be included with include Makevariables.mk
at the top of Makefile
. This variables file contains only the stuff to be edited by developer or per project (e.g. docker image names etc), so that the main makefile becomes easier to port to other repositories, and indicates better which variables are meant to be customized.
860b3e1
to
b683c7f
Compare
Most of the targets – or at least their logic – were extracted to e2e/kind.mk and e2e/Makefile. Most variables were extracted into Makefile.vars.mk
b683c7f
to
6ed4b90
Compare
Summary
Re-organized the Makefile with regards to #198 .
Left to do:
./Makefile
into another fileChecklist
bug
,enhancement
,documentation
,change
,breaking
,as they show up in the changelog
Update tests.