You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NUnit adds/removes command line arguments and not all of them are supported by plugin. https://github.com/nunit/docs/wiki/Console-Command-Line
I'm interested in "--agents" and "--labels".
However instead of adding support for this specific argument I think It would be useful to have possibility to modify command line right before project.exec and inject any argument.
The text was updated successfully, but these errors were encountered:
Hi, I've got mixed feeling about allowing generics params because:
it prevents the plugin from enhancing the params (e.g. escaping the params properly)
it prevents other plugins (e.g. opencover) from getting knowledge about these params (currently opencover plugin only requires the full nunit command line so it'd be fine though)
it makes the build less explicit:
extraArgs = "--labels=On --agents=4"
vs
labels = 'on'
agents = 4
I know it's a bit of extra work for each params, but I think that's what makes the difference between this plugin and a plain Exec task 😃
This way could can be a good compromise, where we'll end up with:
ext.labels = 'On'
ext.agents = 4
Note that ext shouldn't be used, as it causes incompatibilities with other plugins cf Itiviti/gradle-msbuild-plugin#53
But the same syntax (with another name/map) would be fine for me.
NUnit adds/removes command line arguments and not all of them are supported by plugin.
https://github.com/nunit/docs/wiki/Console-Command-Line
I'm interested in "--agents" and "--labels".
However instead of adding support for this specific argument I think It would be useful to have possibility to modify command line right before project.exec and inject any argument.
The text was updated successfully, but these errors were encountered: