
SMughal193306 (Community Member) asked a question.
I have the parameter fileNamePattern: set to "". Not including it also creates the same error.
Following this https://community.veracode.com/s/article/Jenkins-Error-Module-list-must-contain-only-top-level-module-ids-for-the-scan article is not a solution. Anyone else run into the same issue and has a fix?
.png)
Was this working before? In the application profile settings, do you have "Do not allow dependencies to be scanned as top-level modules" checked?
Yes. And I do not have such settings present within my application profile:
Are you an admin on the platform? I see this in all applications, however, I am admin. If you are and do not see them, you might reach out to support.
mhm weird. I am an admin.
please help me also...
thanks for sharing...