www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé BOUTEMY <herve.bout...@free.fr>
Subject maintaining analysis Jenkins jobs configuration
Date Tue, 25 Aug 2015 17:51:20 GMT

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)



View raw message