
PGoodrich295806 (Community Member) asked a question.
I want to say, I am trying to follow the instructions with a simple "Point and shoot" mindset without troubleshooting the .war file. Or any of the other files on the veracode .git repo.

PGoodrich295806 (Community Member) asked a question.
I want to say, I am trying to follow the instructions with a simple "Point and shoot" mindset without troubleshooting the .war file. Or any of the other files on the veracode .git repo.

Hi @PGoodrich295806 (Community Member) - It looks like we'll need a bit more info to help better troubleshoot. Can you please contact our support team? https://community.veracode.com/s/contact-support

hello @PGoodrich295806 (Community Member)
Could you please provide more details? are you using a CI/CI pipeline? uploading manually? how approach do you is using?
Depending on approach I can share some examples to help you

I am going down the Learning Path > Static Analysis Quickstart: https://docs.veracode.com/r/Static_Analysis_Quickstart
It instructs you to download a demo application and references the verademo.war file from the veracode git. https://github.com/veracode/verademo/releases. This is where I first see some issues. It looks like the last time it was updated or contributed to was in May of 2023. In the video it pulls the .war file from the 2020 release. I downloaded this file and others from the repo just to try to follow the example verbatim.
I am able to create the application profile with no issues. I run into problems when I manually upload the file to be pre scanned. It seems like whatever file I download related to the verademo instructions, it fails with the same "Error: Unknown error". This is as far as I am able to get when following the learning path for a static scan.
Do you need any other information? Or what else can I answer?
Thank you for your time to look into this post!

Hi @PGoodrich295806 (Community Member) -
We've figured out this issue -
There was a release on the Verademo project that didn't include the packaged WAR file, so it's likely that you probably tried to download and scan the source file instead. We've done a new release that includes all the correct artifacts so hopefully this is corrected now.
Ask the Community
Get answers, share a use case, discuss your favorite features, or get input from the community.
By clicking “Accept All Cookies”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts.
.png)
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
Hi @PGoodrich295806 (Community Member) -
We've figured out this issue -
There was a release on the Verademo project that didn't include the packaged WAR file, so it's likely that you probably tried to download and scan the source file instead. We've done a new release that includes all the correct artifacts so hopefully this is corrected now.