Closed doormalena closed 4 years ago
Hi @doormalena,
thanks for reporting this. The issue is already fixed and an updated version will be published today.
René
Thank you René. Is this fix also fixing the following error? We just saw this one popping up as well in our pipeline.
[ERROR] Cannot read property 'getAnalysis' of undefined
Yes, it will fix that issue as well.
Hey @doormalena,
the errors are now fixed with version 6.2.3 of the task. Please let me know if you see additional problems.
René
Cannot read property 'getAnalysis' of undefined
is still applicable in 6.2.3. The other one we're verifying now.
Hmpf. I missed the combination with the ForceNewBaseline parameter. Sorry about that. I'm fixing this right away.
Right... that is just plain luck (or dumb luck depending on your viewpoint) for finding this. We will verify it also without the override turned on. Thanks.
Its also occurring without the override turned on. Is there a relation with the fact that there is simply no baseline available?
Issue is fixed, the new version will be out in a couple minutes.
When the warnings policy is turned on, and no baseline is available, the extension fails with error
Cannot read property 'filteredWarnings' of null
We are using version 6.2.2 in Azure DevOps Pipelines. Its configured in a Task Group.![image](https://user-images.githubusercontent.com/8328876/72339794-3e4f5600-36c7-11ea-9060-325f9bc538b1.png)
Full debug log: