ChaitanyaChunchu345364 (Community Member) asked a question.
Jenkins job showing following error after the scan finished,
"[21.10.08 17:34:09] The scan finished with policy status 'Pass'.
Ran into problem when generating scan results in Jenkins. Error: [IllegalArgumentException, The credentials are not in the correct format.]
java.lang.IllegalArgumentException: The credentials are not in the correct format.
at com.veracode.http.Credentials.<init>(Credentials.java:62)
at com.veracode.http.Credentials.create(Credentials.java:23)
at com.veracode.apiwrapper.wrappers.UploadAPIWrapper.setUpApiCredentials(UploadAPIWrapper.java:78)
at com.veracode.jenkins.plugin.utils.WrapperUtil.setupCredential(WrapperUtil.java:29)
at com.veracode.jenkins.plugin.utils.WrapperUtil.getBuildInfo(WrapperUtil.java:73)
at com.veracode.jenkins.plugin.VeracodePipelineRecorder.getScanResults(VeracodePipelineRecorder.java:749)
at com.veracode.jenkins.plugin.VeracodePipelineRecorder.perform(VeracodePipelineRecorder.java:385)
at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:99)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
"
.png){kind=logo}
Hello @ChaitanyaChunchu345364 (Community Member) ,
The error message indicates the ID for authenticating with the Veracode Analysis Center is not in the expected format. There is another Community Post that has a similar issue that you can read over if you want. Another suggestion is to ask a question in the @Integrations Group to see if they can provide more details about the Jenkins credentials error.
Jason
Community Support Engineer