www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy <ol...@apache.org>
Subject Re: Sonar & Jenkins jobs
Date Mon, 20 Aug 2012 18:36:27 GMT
2012/8/20 Olivier Lamy <olamy@apache.org>:
> 2012/8/20 Brett Porter <brett@apache.org>:
>> Hi
>>
>> The separate job configuration for Jenkins on analysis.a.o is a bit frustrating -
the normal job admins can't configure it, fix it, or get notified when it fails.
> I agree it's frustrating..
>>
>> I know the build needs to run locally for Sonar, but can we make Jenkins on there
a node of the main set up, that only takes jobs tagged for Sonar, so they could be configured
as separate ones on the main server with all the other config? I can't recall if there was
a reason that wasn't feasible.
> We can have a node running on the analysis vm and marked sonar jobs
> running only only this node.
> But AFAIK nothing will prevent people with karma (all PMCs) to
> configure non sonar jobs running on this node ...
> This will add a bit of traffic on the main Jenkins which is sometimes
> overloaded.
> I can try that if nobody complains on that.
> Comments ?
Oh I remember now an issue.
For non maven jobs (ant etc..), sonar sql user/password are displayed
in the logs in plain text (that's the reason only people with karmas
can see jobs logs in the ui).
>>
>> Cheers,
>> Brett
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

Mime
View raw message