You are viewing a plain text version of this content. The canonical link for it is here.

Posted to builds@apache.org by Hervé BOUTEMY <he...@free.fr> on 2015/08/25 19:51:20 UTC

maintaining analysis Jenkins jobs configuration

Hi,

I understand that analysis Jenkins jobs are run on a separate Jenkins instance 
(on the same machine as SonarQube).

IIUC, on old SonarQube, having access to Jenkins jobs configuration meant 
having access to MySQL credentials
But today, it seems SonarCube credentials are not stored in jobs configuration 
but in server configuration

Wouldn't it be more easy today to let committers maintain their analysis 
jenkins jobs? With a little conventions on how to configure these jobs (that 
should not replace builds.a.o)?

(and avoid loosing time maintaining it for them, like BUILDS-106)

Regards,

Hervé