[jira] [Updated] (RATIS-948) Update Sonar statistics only from the apache repo, not from the forks

["Marton Elek (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RATIS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marton Elek updated RATIS-948:
------------------------------
    Description: 
RATIS-940 enabled the Sonar check for all the commits but it doesn't work for forked repositories (unless somebody set an own SONAR_TOKEN).

The fix is the same as HDDS-2627, we can restrict the execution to the apache repostiroy.

Thanks to [~ljain] who reported this issue:

Example failure:

https://github.com/lokeshj1703/incubator-ratis/runs/716253801

Note: PRs are not affected as they work well (no sonar check there) only the builds of forked repos. 

  was:
RATIS-940 enabled the Sonar check for all the commits but it doesn't work for forked repositories (unless somebody set an own SONAR_TOKEN).

The fix is the same as HDDS-2627, we can restrict the execution to the apache repostiroy.


> Update Sonar statistics only from the apache repo, not from the forks
> ---------------------------------------------------------------------
>
>                 Key: RATIS-948
>                 URL: https://issues.apache.org/jira/browse/RATIS-948
>             Project: Ratis
>          Issue Type: Improvement
>            Reporter: Marton Elek
>            Assignee: Marton Elek
>            Priority: Major
>
> RATIS-940 enabled the Sonar check for all the commits but it doesn't work for forked repositories (unless somebody set an own SONAR_TOKEN).
> The fix is the same as HDDS-2627, we can restrict the execution to the apache repostiroy.
> Thanks to [~ljain] who reported this issue:
> Example failure:
> https://github.com/lokeshj1703/incubator-ratis/runs/716253801
> Note: PRs are not affected as they work well (no sonar check there) only the builds of forked repos. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)