DSpielman196517 (Community Member) asked a question.
What does "Upload and Scan with Veracode is waiting for a checkpoint" mean when the Jenkins plugin is uploading our package to Veracode?
DSpielman196517 likes this.
- Shuning, Veracode Community Manager (Veracode)
Hi @DSpielman196517 (Community Member) , thank you for your question. I am sorry that we haven't got you a response yet. For more visibility into your post, I am forwarding your question to the @Integrations Group, where there might be Community members who have experience to share. In the meantime, if you have made any progress on this issue, please let us know by adding a comment. Thank you!
Expand Post - MarinaK, Integrations Product Manager (Veracode, Inc.)
my profuse apologies for not getting back to you earlier with response to your question. I think you may not be using the Veracode supported Jenkins plugin. Please check the Veracode Help Center for the latest version of Veracode Jenkins plugin. and let us know if you are still seeing the same issues
https://help.veracode.com/r/SR6Zbh48KDeo2rH~Guvpiw/_g4SYeBLZyLguunqgdUP2w
Thank you!
Expand Post - MarinaK, Integrations Product Manager (Veracode, Inc.)
@DSpielman196517 (Community Member) , you may not be using the latest copy of the Veracode Jenkins plugin
- Shuning, Veracode Community Manager (Veracode)
Thanks @MarinaK, Integrations Product Manager (Veracode, Inc.) for responding.
Hi @DSpielman196517 (Community Member), does what Marina shared solve the issue? If it does, would you mind hitting "select as best" at the bottom of her post to help other Community members facing similar issue access the solution faster in the future? If the issue persists, please let us know by adding comments below.
Expand Post - DSpielman196517 (Community Member)
I am using the latest version 18.11.5.8. I continue to have this issue and cannot do simultaneous scans in different sandboxes within the same concurrent Jenkins job. Any other ideas?
- Andrew K., Veracode Support (Veracode, Inc.)
Hi @DSpielman196517 (Community Member)
The Jenkins plugin has been implemented to only execute after the previous build is fully completed. This is the behavior of the plugin. The checkpoint note indicates this waiting period.
Regards
Andy
- DSpielman196517 (Community Member)
This was working before. What happened is that Jenkins made an update and all plugins that were using the old model of the build manager object won't be compatible with concurrent builds. Tons of other plugins are fixing this issue.
After speaking with Veracode they are looking in to it with their engineers and this should be fixed hopefully. For now I have turned off the option to wait for scan results, which doesn't get us much of the plugins features but at least I can kick off multiple sandbox builds either the same Jenkins job until this is fixed.
Expand Post
.png){kind=logo}
This was working before. What happened is that Jenkins made an update and all plugins that were using the old model of the build manager object won't be compatible with concurrent builds. Tons of other plugins are fixing this issue.
After speaking with Veracode they are looking in to it with their engineers and this should be fixed hopefully. For now I have turned off the option to wait for scan results, which doesn't get us much of the plugins features but at least I can kick off multiple sandbox builds either the same Jenkins job until this is fixed.