search

eficode / codesonar-plugin

MIT License
5 stars 1 forks source link

trouble with codesonar plugin after moving a job from jenkins to cloudbees #67

Open mcote-57 opened 4 years ago

mcote-57 commented 4 years ago

the job was successful in regular jenkins, plugin version 2.0.8. when I moved it to my cloudbees instance, the version of the codesonar plugin went up to the latest. then the failures started. CloudBees Jenkins Distribution 2.222.1.1-rolling plugin version - 2.0.9 Here is the command line that fails now: codesonar conditions: [redAlerts(warrantedResult: 'FAILURE')], credentialId: "${CREDENTIALS}", hubAddress: 'xxx', projectName: 'thor/ui/builder/thor', protocol: 'http' I can navigate to the project and see analysis, but the plugin give me this error:

Project by the name thor/ui/builder/thor was not found on the hub

atombrella commented 4 years ago

projectName: 'thor/mp/builder/thor' but you write thor/ui/builder/thor? I think it's difficult to see exactly what's wrong now without the analyze command, as well. If you don't want to share this information on public Github, you're welcome to write me an email: mads.jensen@eficode.com

mcote-57 commented 4 years ago

sorry it was just my cut and pasting. the project paths match in my jenkins console log.

atombrella commented 4 years ago

Sorry for the wait! I'm still not quite sure what could be wrong with the setup after the change to the CloudBees instance. It also happens when you just trigger the build manually? I have some attempts to set up some test environment, where "project by the name ... not found on the hub" seem to pop up when the analyze command failed.

mcote-57 commented 4 years ago

I see this when there is a valid run of the build. The analysis report is in the hub. the plugin command doesn't find it. I have tried manually running the codesonar conditions command in jenkins pipeline using all variations of the path to the analysis in the hub without success unless the analysis is at the top level of the hub path. So, this path fails... thor/ui/builder/thor, so does thor alone, or just ui/builder/thor. but if I set the build to create the analysis at thor/builder_mp_ui, it is found with no problem.