-
Bug
-
Resolution: Not A Defect
-
Minor
-
jenkins Jenkins 2.303.1
codesonar plugin 2.1
codesonar Release 5.4, Patchlevel 0
Hi
If i create a empty jenkins project and add just a codesonar step to the "Post-build Actions"
I get the following error.
Started by user
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building in workspace C:\Users\auto-rdbuilds\.jenkins\workspace\CodesonarTest
[Codesonar] Using hub URI: "correct url"
ERROR: Step 'Codesonar' failed: unexpected element (uri:"", local:"project"). Expected elements are <{}alert>,<{}analysis>,<{}warning>
Finished: FAILURE
Attatched is the job config
Kind regards
Jens
[JENKINS-66674] Plugin reports "unexpected element"
Assignee | Original: Eficode [ eficode ] | New: gt_dbechtold [ gt_dbechtold ] |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
The plugin code has changed since this issue was originally posted, so I think the behavior is now different. From what I interpret from the original description of this issue, the user has created an empty Freestyle project named "project" and added a mostly empty CodeSonar plugin invocation as a Post-build Action. It appears that the user specified "correct url" as the Hub Address parameter.
With version 3.3.1, I notice the following behaviors, all of which I think are acceptable and actionable:
In the last case above, the error is produced since the plugin is trying to search for the analysis project file/directory within the Jenkins working directory on the agent and no analysis output can be found.
I think the error messages could be made more user-friendly, but I don't think the error messages are exactly unfriendly in this context. I don't think there is anything here that needs fixing, but we will can consider improving the error messages in a future release.
Please reopen this issue if you disagree with my assessment.