← Back to team overview

canonical-ci-engineering team mailing list archive

Re: Migration of s-jenkins to new hardware

 

On Tue, Oct 8, 2013 at 4:38 AM, Sergio Schvezov
<sergio.schvezov@xxxxxxxxxxxxx> wrote:
>>     > As it is, it's cached everywhere on the web[1] just in case
>>     > obfuscating it brings in a sense of security.
>>
>> I don't think anyone feels it's secured by obscurity, it's as secured as
>> the VPN access.
>
>
> Exactly, the VPN gives us the security we need; I was referring to the
> obfuscation above, so in the case of the rebuild button I would just use the
> IP instead of s-jenkins[1].

I would agree, that's why I left the rebuild link as is. Otherwise,
everyone has to maintain their hosts file just to access the rebuild
link.

Francis

> Cheers
> Sergio
>
> [0]
> http://bazaar.launchpad.net/~private-ps-quality-team/jenkins-launchpad-plugin/trunk/view/head:/jlp/jenkinsutils.py#L361
> [1] fun fact: s is legacy for when we had a staging jenkins.



-- 
Francis Ginther
Canonical - Ubuntu Engineering - Quality Engineer


References