-
-
Notifications
You must be signed in to change notification settings - Fork 287
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
CLI argument to support custom naming of generated history files #651
Comments
Hi @Abi-Rai is it really necessary to customize the name of the history files. I would suggest you use a different directory for the history files in your pipeline. Does that for work for you? I'm always trying to avoid new command line parameters. If I would add every requested parameter, the list would be become very long and nobody has the time to look through all the parameters. |
Wow, thank you for the quick response.
Funnily enough my goal was to create a predefined command and distribute it to my team (devs/non-devs) to run as part of their workflow, and I would create a pipeline step that would generate reports that we actually want to keep a history of. And with a preconfigured command they wouldn't need to spend time learning ReportGenerator's commands and could just focus on using the generated report.
With this approach, each time a report is generated with Perhaps having an argument that disables generation of history files and |
Would the following pattern work for you:
|
Yes! that would work. |
Just made the necessary changes in the code base to support that pattern. You will be able to apple the custom text with the following command line parameter: "settings:HistoryFileNamePrefix=YOURCUSTOMTEXT" See also: |
Thank you, especially for pushing it out so quick, not to mention on the same day the issue was raised! |
New version 5.2.2 is now available. |
Thank you! |
Hi! I absolutely love the tool.
This is a feature request for
The use case is the ability to have a specific folder where the reports collect/store historic data for the report and be able to add that folder to .gitignore so that most locally generated historic files are not tracked, but historic files generated in pipelines would be tracked by using glob patterns.
The text was updated successfully, but these errors were encountered: