search

eficode / codesonar-plugin

MIT License
5 stars 1 forks source link

Potential clash with two jobs with the same project name #76

Closed atombrella closed 4 years ago

atombrella commented 4 years ago

A user reports:

It appears that the Jenkins plugin simply checks the latest analysis. If there are 2 builds writing to the same hub project, this can cause problems.

For instance, if one of the builds fails or stalls the scan after the 2nd build has succeeded, the 2nd build will fail because the plugin is checking the other builds analysis results.

There should be a tighter linkage between the analysis run for the build and the plugin checking for Jenkins.

Either, this should be discussed in the documentation for the plugin. When starting the analysis, you don't get a token back that would be the obvious solution for this.

atombrella commented 4 years ago

Based on feedback, this is solved by adding a note in the documentation to add either a suffix or a prefix to the project name, when there are two or more Jenkins jobs using the same project in COdeSonar.