james π― (Community Member) asked a question.
Veracode Flaw Importer build task for TFS 2017 fails with error: "TypeError: Cannot read property 'templateName' of undefined."
Verbose mode doesn't give much more information that that. The two relevant lines that I can find in the log output are as follows:
Class Name : WorkItemCreatoroAuth , Method Name : checkTemplateandAssignWIStatus
(node:8300) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'templateName' of undefined
The task fails immediately after that error. The upload and scan build task completes successfully prior to the import task, but for some reason this one gives an error. Not quite sure where to go from here without some kind of insight into what the task is trying to do...
.png){kind=logo}
Hello @james π― (Community Member)β,
I just published a knowledge base article that I think will answer this question for you. Please take a look at the link below and let me know if this helps:
https://community.veracode.com/s/article/Veracode-Flaw-Importer-build-task-for-TFS-2017-fails-with-error-TypeError-Cannot-read-property-templateName-of-undefined
Hello @Matthew, Customer Support (Veracode)β Thanks for your help. Another group manages the TFS infrastructure for our organization so I don't have a ton of visibility, but after talking to one of the people in that group I was able to discern that upon downloading our process template (Agile), it does not have a Classification.xml file. I'm not sure why that would be, perhaps it's a TFS version issue, a migration issue (we migrated from a local to a shared infrastructure recently), or an issue from upgrading our infrastructure between TFS versions? Through looking at some of your docs, I see that there are some variables that can be defined for templates, is there any way to potentially hotwire this issue by defining variables and whatnot? Kind of grasping at straws now unfortunately since I don't have much power over our TFS infrastructure.
Another question, in your knowledge base article, it looks like you were using a custom Agile process template. Was that derived from the base Agile template? Like I said, our Agile template doesn't have the Classification.xml file in it so I'm curious if that's missing because it's the built-in Agile template or if it should be there regardless. Thanks for all your help!