I am using the VSTS Tasks and the CI Framework.
Sometimes the VSTS Task is behaving different than the CI Framework PowerShell.
But the logging output to the VSTS tasks is pretty limited. It would be helpful, if the LogLevel could be at least set to "Info".
As I understood the VSTS task is also "just" calling a PowerShell script. Would it be possible to extend the parameters to increase the Logging level?
Example: I am using the WebResource Update task and it fails after a while with the message "found 2 webresources with that name". But since i don't know which file he has searched for out of the 50, it will be hard to find the failing one. At the moment I can't validate this with the CI Framework, since this is already requiring a Solution (so it is a newer version).
I am using the VSTS Tasks and the CI Framework. Sometimes the VSTS Task is behaving different than the CI Framework PowerShell.
But the logging output to the VSTS tasks is pretty limited. It would be helpful, if the LogLevel could be at least set to "Info".
As I understood the VSTS task is also "just" calling a PowerShell script. Would it be possible to extend the parameters to increase the Logging level?
Example: I am using the WebResource Update task and it fails after a while with the message "found 2 webresources with that name". But since i don't know which file he has searched for out of the 50, it will be hard to find the failing one. At the moment I can't validate this with the CI Framework, since this is already requiring a Solution (so it is a newer version).