-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Fail to run cmake and protobuf targets from Unix playbook #767
Comments
Hmmm yes that's potentially an issue. What's the use case for wanting to run individual ones like that in the playbook? |
I have a machine that is missing protobuf and I don't want to waste time running the entire playbook to get one role. |
Doesn't the playbook 'skip' everything that's already in place? |
@karianna It does but takes a bit longer than is ideal (An issue I'd quite like to look at...) |
The cmake, ccache and protobuf tasks, in their respective roles, are all tagged with cmake, ccache and protobuf respectively. So these specific roles can be run using Are there any plans to add protobuf back into |
Up until a week ago it wasn't required by AdoptOpenJDK but since the JITserver support went into the extensions repository a few days ago it is (Linux/x64 only for now) so yeah I'll chuck in a PR to re-enable it ... |
@jdekonin Protobuf has been added back as a role, so the use of the option |
Yes, although it looks like there is still an extra role to install protobuf on line 52 that needs to be cleaned up. Its the role in this (current) form that cannot be omitted. |
Good point @jdekonin - with the desire to build with GCC7 where possible that needs to be removed now |
The |
Attempting to run the specific tags for either ccache or protobuf fail to be found.
This change appears to be what caused the issue;
#584
The text was updated successfully, but these errors were encountered: