-
Notifications
You must be signed in to change notification settings - Fork 42
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
Included build task ':reportScoverage' was never scheduled for execution. #98
Comments
Please could you provide an example repository? There's nothing immediately obvious from the above. Thanks, |
I'm seeing something similar, also in a project using composite builds. Building the same project without composite builds works fine. |
Works fine for me. @marcintustin @s4nk Please provide us with more information on your builds; i.e, |
@eyalroth I'm facing the same issue on a Jekins instance where we're testing 4 different projects as a composite build. Please find additional information below. I'm using the recently published version of the plugin. Please let me know if you need any other or more information Debug-Log:
Folder Structure: Executed Command:
build.gradle (excerpt):
settings.gradle:
|
@johanneshiry could you provide the build and settings files for all of the projects (subproject1, subproject2, etc)? My guess would be that the plugin is defined only on some projects but not all, and therefore invoking the entire composite build with |
thanks for the fast reply @eyalroth! you're right the plugin is only defined in subproject1 as this is the only one that also contains scala code. subproject2 and subproject3 are java-only projects and hence there is no need for a scala code coverage check (neither is there a This leads me to the following two questions:
I'll try to execute a the command without |
update 1 update 2 |
update3 spec task
test task commands that fail
command that works (but neglect java tests and hence is not an option)
|
The plugin should only be applied on modules with Scala code or on parent modules (in a multi-module project) that aggregate the reports of sub-modules with Scala code. I don't believe there should be a different behavior for composite builds; i.e, only applye plugin on the modules inside your projects that require it.
With a multi-module project build, all you have to do is add the task name to the command, and gradle will make sure to run the task only in the relevant modules that have it. I'm not sure why the composite build behaves differently.
Did you try running with
But you always executed from the "mainproject" which has the plugin and the task, correct? Could you provide some graph trees for the commands you're trying? You can just add Honestly though, the best thing would be to create a repository with minimal conditions needed for reproduction. I know it's a lot to ask, but that would be the easiest way to identify the problem. |
@eyalroth I'm traveling the whole week and don't know if I can provide answers to your questions and a sample project within this week. Will report back asap. |
@johanneshiry It's ok, there's no rush. Travel safe :) |
yep - didn't make any difference :-(
yep
|
@johanneshiry The good news is that I've been able to identify the culprit, have reduced the sample project into a much simpler structure and added tests for this in #132. The bad news is that it seems that this is caused due to a bug with composite builds (gradle/gradle#11747). Furthermore, your build is incompatible with scoverage for other reasons as well; (a) it uses Scala 2.13, which is currently not working; (b) it uses ScalaTest instead of JUnit, which I'm not sure is compatible with this plugin. For more information on how to setup scala tests using JUnit, check out my example project. |
On ScalaTest - I think that if you take the same approach as the That plugin replaces the implementation of the I think the sample project uses the On the 2.13 issue, for my part, I'm still looking at a way to make this all just work. Sorry. |
I get the error "Included build task ':reportScoverage' was never scheduled for execution.", with the following output from gradle:
The only thing unusual about this project is that
settings.gradle
includes the line:Please advise. Happy to provide more details.
The text was updated successfully, but these errors were encountered: