We have a project that in GitHub that is not receiving PR decorations due to the following error:
Failed to report status to Devops platform because the configured repository slug does not have the expected format 'organization/repository'
Checking the project settings I see that the Repository Name property does have the correct organization/repository format. We have Sonar set up under our DevOps Platform Integrations and the configurations are valid. Checking the ce logs only shows the following information:
Pull request decoration failed java.lang.IllegalStateException: the configured repository slug does not have the expected format 'organization/repository': 'https://github.com/[organization]/[repositoryName]
I’ve seen this previous conversation on the same issue, but their problem seems to have been resolved outside the thread with no general resolution posted.
We are currently running:
SonarQube server v10.2.1
sonarqube-scanner v4.2.1
This log message makes it look like the value supplied for the Repository Name in the Project Settings is literallyhttps://github.com/[organization]/[repositoryName], instead of organization/repositoryName.
Could that be all that is going on here?
I don’t want to forget to mention that your version is past EOL! You should upgrade to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:
Sorry, I just left [organization] and [repositoryName] like that for confidentiality. The actual error message displays the expected text for both of those values.
Do you have any recommended steps that might be able to determine the cause of the issue or a potential fix?
My point was that the error message was showing https://github.com..., as if the full URL is being used for the Repository Name. It should not be (the expect format is organization/repositoryName, not the full URL).
Are you using the full URL as the Repository Name?
Just for the heck of it – I suggest resetting the value (even to a bad value you know will fail) to see if it impacts the error message in your ce.log. The value should be getting taken as-is from that field.
It appears that the issue has just disappeared on its own. We didn’t change any more settings in the last day or so, and haven’t update the project in any way that might fix this. Very mystifying.
