-
-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Reduce travis load by replacing an exclusive grep with an inclusive grep #10964
Conversation
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
@@ -12,6 +12,7 @@ TRAVIS_COMMIT_RANGE="${TRAVIS_COMMIT_RANGE:-HEAD~1..HEAD}" | |||
# Extra variables | |||
LOCAL_BRANCH=$(git rev-parse --abbrev-ref HEAD) | |||
QMK_CHANGES=$(git diff --name-only -n 1 ${TRAVIS_COMMIT_RANGE}) | |||
NUM_CORE_CHANGES=$(echo "$QMK_CHANGES" | grep -Ec -e '^Makefile' -e '^[^/]*.mk' -e '^drivers/' -e '^lib/atsam' -e '^lib/lib8tion/' -e '^platforms' -e '^quantum' -e '^tests' -e '^tmk_core') |
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 have understood the grep correctly, are the submodules excluded here for a reason?
I can see a valid cases both ways:
- we want to build everything when a submodule changes to check for compatibility
- users unknowingly push old/wrong submodules
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'm happy to go either way here. I don't have a reason to have excluded them other than initially pulling in things that are actually in qmk_firmware.
For #2 we might be better off having a lint check anyway.
…rep (qmk#10964) * add -n to avoid compiling * switch to an include rather than exclude strategy
…rep (qmk#10964) * add -n to avoid compiling * switch to an include rather than exclude strategy
Description
Currently a lot of things trigger full builds that shouldn't. This changes our core code identification strategy from "all directories we haven't excluded" to "all directories we have explicitly included."
Types of Changes
Checklist