I opened https://issues.apache.org/jira/browse/SLING-9414 
<https://issues.apache.org/jira/browse/SLING-9414> to allow to disable 
SonarQube for this job.

> On 30. Apr 2020, at 21:44, Konrad Windszus <[email protected]> wrote:
> 
> I had a closer look and the funny thing is that this fails not during the 
> regular build but during the SonarQube build. As that one is executed on an 
> arbitrary node, the build fails.
> The concrete mvn invocation looks like this
> 
> mvn -U clean verify sonar:sonar -Dsonar.host.url=https://sonarcloud.io 
> -Dsonar.organization=apache -Dsonar.projectKey=apache_sling-site 
> -Pjacoco-report 
> -Dsonar.coverage.jacoco.xmlReportPaths=target/site/jacoco-merged/jacoco.xml 
> -Ppublish-site '-Dmsg=Automatic website deployment from 
> https://builds.apache.org/job/Sling/job/sling-site/job/master/339/'
> 
> IMHO SonarQube does not make too much sense for the Sling site, therefore I 
> would rather disable that for the site.
> Don't know if that is feasible already via the Sling module descriptor: 
> https://cwiki.apache.org/confluence/display/SLING/Sling+module+descriptor.
> 
> @Robert: Do you know why that only started failing only recently?
> 
> Konrad
> 
> 
>> On 27. Apr 2020, at 16:47, Konrad Windszus <[email protected]> wrote:
>> 
>> This used to work for previous commits 
>> (https://github.com/apache/sling-site/commits/asf-site) so I guess something 
>> changed with the Jenkins node...
>> 
>> I guess INFRA needs to look into that.
>> 
>>> On 27. Apr 2020, at 16:05, Bertrand Delacretaz <[email protected]> 
>>> wrote:
>>> 
>>> Hi,
>>> 
>>> Just as I was looking at it for other reasons, the sling-site build
>>> started being marked as failed [1], due to
>>> 
>>> empty ident name (for <[email protected]>) not allowed
>>> 
>>> Does anyone have a clue how to fix this?
>>> 
>>> git config user.email (and user.name) would fix this but I don't know
>>> how to run that or where to supply a git config file.
>>> 
>>> That build is using the maven-scm-publish-plugin.
>>> 
>>> -Bertrand
>>> 
>>> [1] see the "maven-scm-publish-plugin:1.1:publish-scm (publish-site) @
>>> sling-site" section at
>>> https://builds.apache.org/job/Sling/job/sling-site/job/master/335/console
>> 
> 

Reply via email to