Forum Discussion
tomdbarker
Nov 25, 2022Copper Contributor
Defender for Cloud DevOps, Currently in Preview, Appears to be Broken Again
Adding the Task in our CI pipelines (previously working on default settings), now results in various errors, starting with Binskim fails (see below): BinSkim completed with exit code 1 ##[er...
tomdbarker
Dec 02, 2022Copper Contributor
Hi Safeena, thanks for replying.
Yes the entire Task fails as a result of the Binskim failure.
Which product do I raise the support ticket against pls?
The way that the DevOps Task works involves almost no configuration on our part at the moment. The Task is added to the build pipeline, and it runs the various default scans. It was working, then it wasn't. The default Task downloads the Nuget package which extracts all the tools and runs them with a pre-configured set of options that are presumably just built into the Task itself. Either way, it's broken.
It would be much more helpful is there was a living doc somewhere that the Preview dev team kept updated so that we could keep track of things, and potentially even add our own configuration(s); if and when that becomes possible.
Yes the entire Task fails as a result of the Binskim failure.
Which product do I raise the support ticket against pls?
The way that the DevOps Task works involves almost no configuration on our part at the moment. The Task is added to the build pipeline, and it runs the various default scans. It was working, then it wasn't. The default Task downloads the Nuget package which extracts all the tools and runs them with a pre-configured set of options that are presumably just built into the Task itself. Either way, it's broken.
It would be much more helpful is there was a living doc somewhere that the Preview dev team kept updated so that we could keep track of things, and potentially even add our own configuration(s); if and when that becomes possible.
tomdbarker
Jan 23, 2023Copper Contributor
so..... it's 7 weeks down the line and nothing has changed pffffff