-
Notifications
You must be signed in to change notification settings - Fork 826
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
introduce make help
as default make recipe
#3888
Conversation
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
Codecov Report
@@ Coverage Diff @@
## master #3888 +/- ##
==========================================
- Coverage 38.62% 38.53% -0.09%
==========================================
Files 167 167
Lines 13734 13734
==========================================
- Hits 5305 5293 -12
- Misses 7998 8003 +5
- Partials 431 438 +7 see 7 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
make help
which print help message as default make recipemake help
which print help message as default make recipe
6eefdae
to
25fc391
Compare
make help
which print help message as default make recipemake help
as default make recipe
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
/cc @g1eny0ung PTAL |
I will look at it this afternoon and this evening. |
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.
The rest LGTM. As it's too late, I'll check it again this morning.
hack/local-up-chaos-mesh.sh
Outdated
@@ -107,7 +107,7 @@ fi | |||
|
|||
if [ -z "$SKIP_IMAGE_BUILD" ]; then | |||
echo "info: building docker images" | |||
IMAGE_REGISTRY_PREFIX=$IMAGE_REGISTRY_PREFIX IMAGE_PROJECT=chaos-mesh IMAGE_TAG=$IMAGE_TAG UI=1 SWAGGER=1 make image | |||
IMAGE_REGISTRY_PREFIX=$IMAGE_REGISTRY_PREFIX IMAGE_TAG=$IMAGE_TAG UI=1 SWAGGER=1 make image |
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.
IMAGE_REGISTRY_PREFIX=$IMAGE_REGISTRY_PREFIX IMAGE_TAG=$IMAGE_TAG UI=1 SWAGGER=1 make image | |
IMAGE_TAG=$IMAGE_TAG UI=1 SWAGGER=1 make image |
If I understand correctly, now we are no longer providing the ability to customize the registry, and some targets with docker-push
prefix also are being removed.
I agree with these changes, since it's easy to rename the image name with docker image tag
, we don't need to keep these seemingly convenient, but somewhat redundant targets.
So the IMAGE_REGISTRY_PREFIX
env should be removed here as well as others.
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.
If I understand correctly, now we are no longer providing the ability to customize the registry, and some targets with
docker-push
prefix also are being removed.
Yeah, that's the thing I want to do: do NOT provide the flags/ENVs for configuring different registry/repo, but only during the building process.
It seems the changes in local-up-chaos-mesh.sh
is NOT a part of building things but installing things.
So maybe it's better to revert the changes in local-up-chaos-mesh.sh
.
If necessary, I would open another PR for similar changes, but for installing scripts like install.sh
, local-up-chaos-mesh.sh
and other .sh scripts.
What do you think about it? Reverting changes in local-up-chaos-mesh.sh
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.
What do you think about it? Reverting changes in local-up-chaos-mesh.sh
I still don't think it's necessary because these scripts are used more for debugging purposes, and giving them more configurable items is often redundant. As I said above:
I agree with these changes, since it's easy to rename the image name with docker image tag
, we don't need to keep these seemingly convenient, but somewhat redundant targets.
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.
So, keep modifying it like this. :) 🔧
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.
@STRRL Only this place is not updated, after the update I will approve this PR.
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.
Hi @g1eny0ung , I actually prefer to revert changes in local-up-chaos-mesh.sh
in this PR.
I totally agree with your opinion. But it's a little out of the scope from this PR.
I would do it, but in another new PR. Not carry changes in .sh
files in the PR.
What do you think about it?
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.
But it's a little out of the scope from this PR.
@STRRL That sounds reasonable. I agree that we can wrap up the .sh
modifications in the upcoming PR.
…tion Signed-off-by: STRRL <im@strrl.dev>
Signed-off-by: STRRL <im@strrl.dev>
…enerating Signed-off-by: STRRL <im@strrl.dev>
Cool! I have run this pr on the environment, The |
Signed-off-by: STRRL <im@strrl.dev>
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!
/merge |
@chaos-mesh/maintainers @chaos-mesh/committers Please be aware that any additions or removals of make targets in the |
What problem does this PR solve?
close #3769
What's changed and how it works?
In this PR, we provide a target called
make help
like this:Related changes
UI interface
Checklist
CHANGELOG
CHANGELOG.md
Tests
Side effects
DCO
If you find the DCO check fails, please run commands like below (Depends on the actual situations. For example, if the failed commit isn't the most recent) to fix it: