<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:15:44 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-1763] Sonarcloud analysis not updating GitHub PR and Checks</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1763</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;I&apos;ve received and confirmed multiple cases in which results of Sonarqube analysis are not updated on Github PRs even though the analysis is successfully run and processed by Sonarcloud.    Symptoms of this include a Sonarcloud status of &quot;queued&quot; on Github.  The issue appears to be intermittent and may indicate a bug on the Sonarcloud end.&lt;/p&gt;

&lt;p&gt;The Maven-based scans do update the Checks tab. However their scans seem erratic.&lt;/p&gt;</description>
                <environment></environment>
        <key id="81087">FOLIO-1763</key>
            <summary>Sonarcloud analysis not updating GitHub PR and Checks</summary>
                <type id="10001" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium">Bug</type>
                                            <priority id="10001" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p2.svg">P2</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="61cd0ca0bce5e00069e98be7">David Crossley</assignee>
                                                                <reporter accountid="5f9abc1eb45b2e007453f423">John Malconian</reporter>
                                    <labels>
                            <label>ci</label>
                            <label>platform-backlog</label>
                    </labels>
                <created>Thu, 31 Jan 2019 14:16:55 +0000</created>
                <updated>Wed, 3 Jun 2020 16:39:27 +0000</updated>
                            <resolved>Thu, 28 Feb 2019 06:03:03 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                <comments>
                                                            <comment id="195102" author="5f9abc1eb45b2e007453f423" created="Mon, 4 Feb 2019 14:21:58 +0000"  >&lt;p&gt; I notice that this ui-requests PR doesn&apos;t invoke the Sonarqube scan - &lt;a href=&quot;https://jenkins-aws.indexdata.com/job/folio-org/job/ui-requests/job/PR-234/2/&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://jenkins-aws.indexdata.com/job/folio-org/job/ui-requests/job/PR-234/2/&lt;/a&gt; - So that&apos;s an obvious problem to investigate first, I think. &lt;/p&gt;</comment>
                                                            <comment id="195104" author="5f9abc1eb45b2e007453f423" created="Mon, 4 Feb 2019 19:04:54 +0000"  >&lt;p&gt;I see the following warning in Sonarcloud for branches of UI projects.  Not sure what is going here.&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Could not find ref &apos;master&apos; in refs/heads or refs/remotes/origin. You may see unexpected issues and changes. Please make sure to fetch this ref before pull request analysis.
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;&lt;a href=&quot;https://sonarcloud.io/project/issues?branch=stcom-365-mcl-aria-roles&amp;amp;id=org.folio%3Astripes-smart-components&amp;amp;resolved=false&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://sonarcloud.io/project/issues?branch=stcom-365-mcl-aria-roles&amp;amp;id=org.folio%3Astripes-smart-components&amp;amp;resolved=false&lt;/a&gt;&lt;/p&gt;
</comment>
                                                            <comment id="195106" author="5f9abc1eb45b2e007453f423" created="Mon, 4 Feb 2019 19:32:19 +0000"  >&lt;p&gt;This seems to resemble some of the issue we are seeing:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://community.sonarsource.com/t/pr-decoration-for-github-no-longer-working/5875/7&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://community.sonarsource.com/t/pr-decoration-for-github-no-longer-working/5875/7&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="195109" author="61cd0ca0bce5e00069e98be7" created="Tue, 5 Feb 2019 00:57:13 +0000"  >&lt;p&gt;Regarding the part above about &quot;ui-requests PR doesn&apos;t invoke the Sonarqube scan&quot;.&lt;br/&gt;
Would that be because for ui-* modules the &quot;config.runSonarqube&quot; is false by default, and ui-requests/Jenkinsfile does not switch it on. Whereas for example ui-agreements does have it true, and its scan did run on a recent PR.&lt;/p&gt;</comment>
                                                            <comment id="195112" author="5f9abc1eb45b2e007453f423" created="Tue, 5 Feb 2019 01:35:33 +0000"  >&lt;p&gt;That sounds about right.   Unlike the Maven modules,  Sonarqube analysis is an optional config parameter for Stripes/UI modules that is false by default (although it probably &lt;b&gt;should&lt;/b&gt; be true by default).  &lt;/p&gt;

&lt;p&gt;Aside from the ui-requests issue, however, I think that I am seeing that no Sonarqube analysis is actually processed on Sonarcloud for any of the UI/Stripes modules on non-master branches and pull requests.     For example:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://sonarcloud.io/project/issues?branch=UICHKIN-75&amp;amp;id=org.folio%3Aui-checkin&amp;amp;resolved=false&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://sonarcloud.io/project/issues?branch=UICHKIN-75&amp;amp;id=org.folio%3Aui-checkin&amp;amp;resolved=false&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Sonarqube reports &quot;no issues&quot;,  but I don&apos;t think any thing is actually processed. &lt;/p&gt;

&lt;p&gt;Also,  for Maven modules,  Sonarcloud processing seems hit or miss.  &lt;/p&gt;

&lt;p&gt;The problems started to occur two-three weeks ago after Sonarcloud made some significant changes to how results are analyzed and how Github PRs are decorated.   There may be some hints at the end of this thread - &lt;a href=&quot;https://community.sonarsource.com/t/pr-decoration-for-github-no-longer-working/5875/7&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://community.sonarsource.com/t/pr-decoration-for-github-no-longer-working/5875/7&lt;/a&gt; - but we may need to post an inquiry to the community board. &lt;/p&gt;</comment>
                                                            <comment id="195116" author="61cd0ca0bce5e00069e98be7" created="Tue, 5 Feb 2019 02:11:28 +0000"  >&lt;p&gt;Here is another useful report, having similar symptoms, and active today:&lt;br/&gt;
&lt;a href=&quot;https://community.sonarsource.com/t/sonarcloud-doesnt-update-github-status/6325&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://community.sonarsource.com/t/sonarcloud-doesnt-update-github-status/6325&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="195119" author="61cd0ca0bce5e00069e98be7" created="Tue, 5 Feb 2019 12:10:21 +0000"  >&lt;p&gt;So how are the Sonar scans run for those other ui-* modules that are not configured in their Jenkinsfile.&lt;/p&gt;</comment>
                                                            <comment id="195121" author="61cd0ca0bce5e00069e98be7" created="Tue, 5 Feb 2019 12:10:50 +0000"  >&lt;p&gt;I confirm that processing seems to be not happening for non-master branches and PRs. Looking at ui-circulation today, there are 17 issues reported for a master branch build, but none for the recent PR and its branch.&lt;/p&gt;</comment>
                                                            <comment id="195124" author="61cd0ca0bce5e00069e98be7" created="Tue, 5 Feb 2019 12:11:24 +0000"  >&lt;p&gt;The linked community posts mention ensuring doing &apos;git fetch&apos; before running sonar-scanner. We use the Jenkins &quot;checkout&quot; function, so i presume that it is doing that.&lt;/p&gt;

&lt;p&gt;Investigated our Jenkins &quot;Checkout&quot; stage to try to find any difference between the Maven-based builds and the NPM-based builds. The vars/buildNPM.groovy has an extra section &quot;RelativeTargetDirectory&quot; added a couple of months ago, but only merged 9 days ago with jenkins-pipeline-libs/pull/57 (
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1596&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1596&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;enable platform builds for all ui-* modules PRs in CI&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1596
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
).&lt;/p&gt;

&lt;p&gt;I am not clear what that does, but wonder if that could that be the cause?&lt;/p&gt;</comment>
                                                            <comment id="195128" author="61cd0ca0bce5e00069e98be7" created="Thu, 7 Feb 2019 06:16:55 +0000"  >&lt;p&gt;Here is our post today to the SonarSource Community forum:&lt;br/&gt;
&lt;a href=&quot;https://community.sonarsource.com/t/sonarcloud-now-not-updating-github-pr-and-now-only-running-on-master-branch/6595&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://community.sonarsource.com/t/sonarcloud-now-not-updating-github-pr-and-now-only-running-on-master-branch/6595&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="195131" author="61cd0ca0bce5e00069e98be7" created="Fri, 8 Feb 2019 00:45:17 +0000"  >&lt;p&gt;We indicated above that sonar is not running on non-master branches and PRs. That seems to be not true. See this one today where i added deliberate new &quot;code smell&quot;:&lt;br/&gt;
&lt;a href=&quot;https://github.com/folio-org/ui-licenses/pull/62&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/ui-licenses/pull/62&lt;/a&gt;&lt;br/&gt;
... it is detecting the new issues.&lt;/p&gt;

&lt;p&gt;So i adusted this issue Summary, and the post title:&lt;br/&gt;
&lt;a href=&quot;https://community.sonarsource.com/t/sonarcloud-now-not-updating-github-pr-and-checks/6595&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://community.sonarsource.com/t/sonarcloud-now-not-updating-github-pr-and-checks/6595&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;He is still puzzled about why the Sonar result is not reported back to GitHub Checks for the NPM-based builds.&lt;/p&gt;

&lt;p&gt;He asked if it is happening consistently. I said yes. If anyone sees any differently then please show an example branch/PR.&lt;/p&gt;</comment>
                                                            <comment id="195134" author="5f9abc1eb45b2e007453f423" created="Fri, 15 Feb 2019 15:43:50 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt; I believe I&apos;ve made some significant progress on this issue.  &lt;/p&gt;

&lt;p&gt;&lt;b&gt;Github PR decoration for NPM-based builds&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;There is a command (&apos;npm version&apos;) in the NPM build pipeline that is executed prior to Sonarqube analysis that makes a git commit on the Jenkins checkout during the build.  This commit updates the SHA1 of HEAD so that it no longer matches the original PR SHA1 on Github and, therefore, confuses Sonarqube.   I&apos;ve added the option &apos;--no-git-tag-version&apos; to the command in the shared pipeline libraries so that no git commit is made during the build.   The result is that SonarCloud GitHub PR decoration now works on NPM-based PRs.  &lt;/p&gt;

&lt;p&gt;&lt;b&gt;The Sonarcloud/Sonarqube Scanner warning &quot;Could not find ref &apos;master&apos; in refs/heads or refs/remotes/origin. You may see unexpected issues and changes. Please make sure to fetch this ref before pull request analysis&quot; that occurs during branch builds on all projects.&lt;/b&gt;&lt;/p&gt;

&lt;p&gt;This warning totally makes sense,  because, unlike PR builds in Jenkins, ref &apos;master&apos; is indeed not fetched on branch builds - only the ref of the branch is fetched.   But Sonarqube now requires ref &apos;master&apos; when scanning branch builds.  The solution was to add the command&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;&apos;git fetch --no-tags ${env.projUrl} +refs/heads/master:refs/remotes/origin/master&apos; 
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt; 
&lt;p&gt;prior to invoking the Sonarqube scan during branch builds (for both Maven and NPM-based builds).    After this modification,  I&apos;ve verified that the warning is no longer generated.  &lt;/p&gt;

&lt;p&gt;I&apos;ve merged these changes into jenkins-pipeline-libs in PR-58.  &lt;a href=&quot;https://github.com/folio-org/jenkins-pipeline-libs/pull/58&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/jenkins-pipeline-libs/pull/58&lt;/a&gt;.   See the PR for exact code changes.   &lt;/p&gt;

&lt;p&gt;I&apos;m going to keep this issue open so that you can monitor the status of these changes over the next few days.  It&apos;s still not entirely clear to me why some Maven-based PRs are intermittently not decorated and if that issue is related to either I&apos;ve the changes I&apos;ve made or something else entirely.    When/If you feel the issues have been adequately resolved, then go ahead and close this issue. &lt;/p&gt;</comment>
                                                            <comment id="195139" author="61cd0ca0bce5e00069e98be7" created="Mon, 18 Feb 2019 05:59:34 +0000"  >&lt;p&gt;That is great news. I have done various PRs today, and the Sonar checks are behaving. Will monitor further.&lt;/p&gt;

&lt;p&gt;If developers see different behaviour then please tell me. On an open PR, the Sonar check result should reported to the &quot;Show all checks&quot; panel of the Conversation tab, and to the actual &quot;Checks&quot; tab (need to refresh page to see the latter).&lt;/p&gt;</comment>
                                                            <comment id="195142" author="61cd0ca0bce5e00069e98be7" created="Mon, 18 Feb 2019 05:59:58 +0000"  >&lt;p&gt;Updated our SonarSource post:&lt;br/&gt;
&lt;a href=&quot;https://community.sonarsource.com/t/sonarcloud-now-not-updating-github-pr-and-checks/6595&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://community.sonarsource.com/t/sonarcloud-now-not-updating-github-pr-and-checks/6595&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="195144" author="61cd0ca0bce5e00069e98be7" created="Tue, 19 Feb 2019 08:51:34 +0000"  >&lt;p&gt;Drat.&lt;/p&gt;

&lt;p&gt;Assessed 38 pull requests since the jenkins-pipeline-libs/pull/58 was merged to master.&lt;br/&gt;
(start:20190215 15:13 UTC .. end:20190219 00:48 UTC)&lt;/p&gt;

&lt;p&gt;30 had the decoration of the Sonar result. 8 did not.&lt;/p&gt;

&lt;p&gt;Of those 8:&lt;br/&gt;
ui-marccat had 4/4 did not decorate&lt;br/&gt;
mod-marccat had 2/3 did not decorate&lt;/p&gt;

&lt;p&gt;Apart from those 6, the other two were:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/folio-org/ui-checkin/pull/164&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/ui-checkin/pull/164&lt;/a&gt; (email notification for opened PR: Mon, 18 Feb 2019 08:11:53 -0800)&lt;br/&gt;
&lt;a href=&quot;https://github.com/folio-org/mod-inventory-storage/pull/246&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/mod-inventory-storage/pull/246&lt;/a&gt; (email notification for opened PR: Mon, 18 Feb 2019 08:30:14 -0800)&lt;br/&gt;
Sequential. Others repos close to that time, both before and after were okay. And mod-inventory-storage PRs had other successfully decorated PRs during the time range mentioned at the start of this Comment.&lt;/p&gt;

&lt;p&gt;Following through to Sonarcloud as Admin for those two repos shows no problems for &quot;Background Tasks&quot;.&lt;/p&gt;</comment>
                                                            <comment id="195148" author="557058:09292aa8-9d37-482b-b244-17349bbbf497" created="Wed, 20 Feb 2019 16:37:45 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=61cd0ca0bce5e00069e98be7&quot; class=&quot;user-hover&quot; rel=&quot;61cd0ca0bce5e00069e98be7&quot; data-account-id=&quot;61cd0ca0bce5e00069e98be7&quot; accountid=&quot;61cd0ca0bce5e00069e98be7&quot; rel=&quot;noreferrer&quot;&gt;David Crossley&lt;/a&gt; it looks like SonarCloud test coverage on the new code had stopped working for ui-orders a while ago (always 0.0%).&lt;br/&gt;
&lt;a href=&quot;https://github.com/folio-org/ui-orders/pull/266&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/ui-orders/pull/266&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://sonarcloud.io/component_measures?id=org.folio%3Aui-orders&amp;amp;pullRequest=266&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://sonarcloud.io/component_measures?id=org.folio%3Aui-orders&amp;amp;pullRequest=266&lt;/a&gt;&lt;/p&gt;</comment>
                                                            <comment id="195151" author="61cd0ca0bce5e00069e98be7" created="Thu, 21 Feb 2019 06:15:04 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A09292aa8-9d37-482b-b244-17349bbbf497&quot; class=&quot;user-hover&quot; rel=&quot;557058:09292aa8-9d37-482b-b244-17349bbbf497&quot; data-account-id=&quot;557058:09292aa8-9d37-482b-b244-17349bbbf497&quot; accountid=&quot;557058:09292aa8-9d37-482b-b244-17349bbbf497&quot; rel=&quot;noreferrer&quot;&gt;Aliaksei Chumakou&lt;/a&gt; Not sure yet if that &quot;coverage on the new code&quot; is related to this 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1763&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1763&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Sonarcloud analysis not updating GitHub PR and Checks&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-1763
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
. I added a new issue at 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1818&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1818&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Sonar analysis &amp;quot;coverage on new code&amp;quot; for PRs of NPM-based repos not happening recently&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10303?size=medium&quot; /&gt;
            FOLIO-1818
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.&lt;/p&gt;</comment>
                                                            <comment id="195153" author="61cd0ca0bce5e00069e98be7" created="Thu, 21 Feb 2019 08:29:38 +0000"  >&lt;p&gt;Assessed the next 46 PRs for relevant repos (up to 20190220 23:43 UTC).&lt;br/&gt;
Apart from 2/2 mod-marccat, these 4 others failed to decorate the PR:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/folio-org/mod-circulation/pull/190&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/mod-circulation/pull/190&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://github.com/folio-org/ui-circulation/pull/255&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/ui-circulation/pull/255&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://github.com/folio-org/ui-erm-usage/pull/47&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/ui-erm-usage/pull/47&lt;/a&gt;&lt;br/&gt;
&lt;a href=&quot;https://github.com/folio-org/ui-licenses/pull/96&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/ui-licenses/pull/96&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;For each of those 4 their analysis was run, just not reported back to PR.&lt;/p&gt;</comment>
                                                            <comment id="195156" author="61cd0ca0bce5e00069e98be7" created="Fri, 22 Feb 2019 08:08:44 +0000"  >&lt;p&gt;Updated our SonarSource post:&lt;br/&gt;
&lt;a href=&quot;https://community.sonarsource.com/t/sonarcloud-now-not-updating-github-pr-and-checks/6595&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://community.sonarsource.com/t/sonarcloud-now-not-updating-github-pr-and-checks/6595&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The helpful Janos at SonarSource replied to my recent summaries. They are investigating at their end.&lt;/p&gt;

&lt;p&gt;It is a great benefit of truly open source that we can actually demonstrate our findings to the post.&lt;/p&gt;</comment>
                                                            <comment id="195159" author="61cd0ca0bce5e00069e98be7" created="Mon, 25 Feb 2019 05:23:22 +0000"  >&lt;p&gt;Found some documentation about this feature change:&lt;br/&gt;
&lt;a href=&quot;https://community.sonarsource.com/t/pr-analysis-results-are-now-displayed-in-the-checks-tab-of-pull-requests-in-github/5870&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://community.sonarsource.com/t/pr-analysis-results-are-now-displayed-in-the-checks-tab-of-pull-requests-in-github/5870&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;As explained there, now the results are summarised and displayed on the Checks tab of the PR. Sonar no longer displays each detected code issue on the front Conversation tab of the PR.&lt;/p&gt;</comment>
                                                            <comment id="195162" author="61cd0ca0bce5e00069e98be7" created="Tue, 26 Feb 2019 03:21:03 +0000"  >&lt;p&gt;In our SonarSource post linked above, Janos provided a &apos;curl&apos; query to verify the decoration. Adding the pattern here for future reference:&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;curl https://api.github.com/repos/folio-org/&amp;lt;repo-name&amp;gt;/commits/&amp;lt;sha1-of-last-commit-in-the-set&amp;gt;/check-runs \
  -H &apos;Accept: application/vnd.github.antiope-preview+json&apos; | jq .
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;</comment>
                                                            <comment id="195166" author="61cd0ca0bce5e00069e98be7" created="Tue, 26 Feb 2019 06:39:22 +0000"  >&lt;p&gt;We reckon that we have solved the apparent &quot;intermittent&quot; decoration of the PR Checks tab.&lt;/p&gt;

&lt;p&gt;After creating a branch for a PR, then the master might be subsequently updated. When our Jenkins is preparing for the sonar scan, the master is merged into the PR head. That of course can make a different SHA1 which does not correlate with the SHA1 that is being decorated with the Sonar result.&lt;/p&gt;

&lt;p&gt;All repositories will now have the branch protection setting &quot;Require branches to be up to date before merging&quot;.&lt;/p&gt;</comment>
                                                            <comment id="195168" author="61cd0ca0bce5e00069e98be7" created="Tue, 26 Feb 2019 06:47:12 +0000"  >&lt;p&gt;To summarise, there were three parts:&lt;/p&gt;

&lt;p&gt;1) An extra commit was being made by our Jenkins when preparing for the scan by doing &apos;npm version&apos;. Instead do &apos;npm --no-git-tag-version version&apos;.&lt;/p&gt;

&lt;p&gt;2) Remove the Warning note:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;Could not find ref &apos;master&apos; in refs/heads or refs/remotes/origin ...&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;by doing the following before doing the Sonar scan:&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;git fetch --no-tags ${env.projUrl} +refs/heads/master:refs/remotes/origin/master
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;3) Add the branch protection setting &quot;Require branches to be up to date before merging&quot;.&lt;/p&gt;</comment>
                                                            <comment id="195170" author="61cd0ca0bce5e00069e98be7" created="Tue, 26 Feb 2019 06:48:52 +0000"  >&lt;p&gt;Now &quot;In review&quot;.&lt;/p&gt;

&lt;p&gt;Will monitor the PRs for the next day.&lt;/p&gt;</comment>
                                                            <comment id="195172" author="61cd0ca0bce5e00069e98be7" created="Thu, 28 Feb 2019 06:02:04 +0000"  >&lt;p&gt;At our SonarSource post:&lt;br/&gt;
&lt;a href=&quot;https://community.sonarsource.com/t/sonarcloud-now-not-updating-github-pr-and-checks/6595&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://community.sonarsource.com/t/sonarcloud-now-not-updating-github-pr-and-checks/6595&lt;/a&gt;&lt;br/&gt;
Janos said:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;At our side, we have the following in progress:&lt;/p&gt;

&lt;p&gt;Improve our monitoring, to make it easier in the future to match strangely behaving analyses with our logs, and making it easier to track down the root cause.&lt;/p&gt;

&lt;p&gt;Improve the way we decorate, to avoid such confusion as you experienced in this thread. Ticket to track: &lt;a href=&quot;https://jira.sonarsource.com/browse/SONARCLOUD-467&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;SONARCLOUD-467&lt;/a&gt; &lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Even if we sign up, cannot see that ticket. So watch the SonarSource &lt;a href=&quot;https://community.sonarsource.com/c/announce&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;Announcements&lt;/a&gt; forum, e.g. there is a beta of automatic analysis.&lt;/p&gt;</comment>
                                                            <comment id="195176" author="61cd0ca0bce5e00069e98be7" created="Thu, 28 Feb 2019 06:03:03 +0000"  >&lt;p&gt;Assessed our next 23 relevant PRs from yesterday, since 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1828&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1828&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Configure each GitHub repository &amp;quot;Require branches to be up to date before merging&amp;quot;&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1828
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 to require branch be up-to-date.&lt;br/&gt;
All did decorate the Checks tab with the Sonar result.&lt;/p&gt;

&lt;p&gt;Some others were still open PRs which did not have the Checks tab with Sonar report. This was because they had not yet done the up-to-date branch requirement.&lt;/p&gt;

&lt;p&gt;All is now well, so closed this ticket.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="81010">FOLIO-1828</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="81106">FOLIO-1823</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10057" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Development Team</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10144"><![CDATA[Core: Platform]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzzdpb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue id="1722">Core: Platform - Sprint 56</customfieldvalue>
    <customfieldvalue id="1148">Core: Platform - Sprint 58</customfieldvalue>
    <customfieldvalue id="1661">Core: Platform - Sprint 57</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10044" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10024" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>[CHART] Date of First Response</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Tue, 5 Feb 2019 00:57:13 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>