[ 
https://issues.apache.org/jira/browse/CALCITE-6928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939993#comment-17939993
 ] 

Alessandro Solimando edited comment on CALCITE-6928 at 4/1/25 9:36 AM:
-----------------------------------------------------------------------

The issue was caused by a partial rotation of the Sonar credentials which 
weren't updated in Jenkins, INFRA team has updated them and I could confirm it 
works with a [green 
run|https://ci-builds.apache.org/job/Calcite/job/Calcite-sonar/job/PR-4282/lastBuild/],
 resolving the ticket


was (Author: asolimando):
The issue was caused by a partial rotation of the Sonar credentials which 
weren't updated in Jenkins, they have updated them and I could confirm it works 
with a [green 
run|https://ci-builds.apache.org/job/Calcite/job/Calcite-sonar/job/PR-4282/lastBuild/],
 resolving the ticket

> Sonar analysis fails in CI
> --------------------------
>
>                 Key: CALCITE-6928
>                 URL: https://issues.apache.org/jira/browse/CALCITE-6928
>             Project: Calcite
>          Issue Type: Task
>            Reporter: Zhen Chen
>            Assignee: Alessandro Solimando
>            Priority: Major
>              Labels: pull-request-available
>
> Sonar analysis has started to fail the 17th of March without any related 
> change in the Apache Calcite project. 
> The relevant extract from the latest failing job 
> ([https://ci-builds.apache.org/job/Calcite/job/Calcite-sonar/job/main/937/]) 
> is as follows: 
> {code:java}
> FAILURE: Build failed with an exception. 
> * What went wrong: 
> Execution failed for task ':sonar'. 
> > Project not found. Please check the 'sonar.projectKey' and 
> > 'sonar.organization' properties, the 'SONAR_TOKEN' environment variable, or 
> > contact the project administrator to check the permissions of the user the 
> > token belongs to  {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to