I have a the PR workflow implemented starting with a baseline scan of my 'master' branch -> from there, developers create a 'feature' branch, edit/modify/create code, add -> commit -> push -> Create PR -> this triggers a Jenkins job running on a remote machine which does not have either the source code from bitbucket or SonarQube on it, it is just* Jenkins - Jenkins job w/params creates the SonarQube invocation w/this plugin... all is working perfectly as configured... However - other developers are not having this plugin detect new issues for the PR when the sonarqube analysis does appear to find them - it reports issues to stash in PostAnalysis job, etc...
I apologize if any of this is rather vague - I have been going through permissions/configurations/account stuff for the last few days for any diff's in privileges but to no avail... appreciate any thoughts/assistance, etc.
EDIT - it appears the wrong Revision is being checked out from Git in some instances...
hax0rdlux3
commented
6 years ago
Hello,
I have a the PR workflow implemented starting with a baseline scan of my 'master' branch -> from there, developers create a 'feature' branch, edit/modify/create code, add -> commit -> push -> Create PR -> this triggers a Jenkins job running on a remote machine which does not have either the source code from bitbucket or SonarQube on it, it is just* Jenkins - Jenkins job w/params creates the SonarQube invocation w/this plugin... all is working perfectly as configured... However - other developers are not having this plugin detect new issues for the PR when the sonarqube analysis does appear to find them - it reports issues to stash in PostAnalysis job, etc...
I apologize if any of this is rather vague - I have been going through permissions/configurations/account stuff for the last few days for any diff's in privileges but to no avail... appreciate any thoughts/assistance, etc.
EDIT - it appears the wrong Revision is being checked out from Git in some instances...