-
Notifications
You must be signed in to change notification settings - Fork 129
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
Add BUILD_PKGS_BLACKLIST? #172
Comments
I have started to implemented this (and other features) in #137 |
Ok, nice. Would you want to keep this one open then, and close after implementation / merge of #137, or close right now as a sort-of duplicate? |
Let's keep it open as a reminder
As a temporary fix you could create a |
Yeah, I tried to do that, but forgot that the Does |
The string gets executed by |
If I'm not mistaken, target repo is read-only so you can't |
|
This would be the opposite of
BUILD_PKGS_WHITELIST
.Example use-case:
motoman_experimental
depends onindustrial_experimental
, for a single package only:industrial_robot_pkg_gen
. Asindustrial_experimental
has not been released, I'm using a.travis.rosinstall
file. Everything works, but:industrial_experimental
also containsIRC_v2
packages, which run a lot of tests.Testing is good, but
motoman_experimental
does not use anything fromIRCv2
, and I'd rather ignore theIRCv2
packages completely in the Travis runs formotoman_experimental
.Instead of having to list each and every pkg I do want tested, it would be nice if we could invert the setting and use a blacklist.
The text was updated successfully, but these errors were encountered: