Skip to content
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

dynamic output path #63

Closed
dddkiran opened this issue Jun 11, 2018 · 3 comments
Closed

dynamic output path #63

dddkiran opened this issue Jun 11, 2018 · 3 comments

Comments

@dddkiran
Copy link

Hey!

We have one diagnostics project for monitoring different products(web1/web2..) in different environments (qa/test/beta).

Is it possible to pass Ghpr.NUnit.Settings.json or output path dynamically though nunit parameters ?

Cherrs,
Kiran

@elv1s42 elv1s42 self-assigned this Jun 11, 2018
@elv1s42
Copy link
Member

elv1s42 commented Jun 11, 2018

Hi @dddkiran,
I had a similar idea more than a year ago and raised an issue in NUnit repository:
nunit/nunit-console#148

The idea was to be able to pass Ghpr settings via NUnit Console command line arguments.

The issue is not resolved at the moment, so I can suggest using some workaround like for example running .ps1 script (which will change .json settings file) as a separate step of your CI process before executing tests.

@elv1s42
Copy link
Member

elv1s42 commented Jul 6, 2018

Closing for now as there is no way to extract arguments from NUnit Console arguments at the moment, and there is a workaround like for example running .ps1 script (which will change .json settings file) as a separate step of your CI process before executing tests.

@elv1s42 elv1s42 closed this as completed Jul 6, 2018
@elv1s42
Copy link
Member

elv1s42 commented Jul 8, 2019

Hi @dddkiran ,

Ghpr.Core now supports mulitple project settings in one config file: https://github.com/GHPReporter/Ghpr.Core#about-settings-file

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants