[guardian-dev] Proposal: Public Jenkins

[Hans-Christoph Steiner]

Having this public jenkins instance to show the data from the private server
would allow us to do all the fun stuff like this, including a sad trombone
sound when someone breaks the build.

.hc

On 04/12/2013 05:33 PM, Mark Belinsky wrote:
> What about setting up the wall display plugin or something similar and have
> that gui be publicly accessible?
> 
> ~Sent from my mobile. Please excuse any typos or terseness.
> On Apr 12, 2013 3:32 PM, "Hans-Christoph Steiner" <hans at guardianproject.info>
> wrote:
> 
>>
>> I've been runing quite a few jenkins instances for a while for puredata.  I
>> find that jenkins can be quite fragile with slaves in the setup.  Since
>> this
>> will be something like a jenkins slave, I would not be surprised if it was
>> also fragile.
>>
>> .hc
>>
>> On 04/12/2013 03:01 PM, Abel Luck wrote:
>>> Once it is setup all the info from our private Jenkins will be mirrored
>>> to the public one. Including the addition of new projects etc.
>>>
>>> So, the only ongoing maintenance required is when Jenkins plugin updates
>>> happen, we need to update them on the public and private instances.
>>>
>>> ~abel
>>>
>>> Hans of Guardian:
>>>>
>>>> I like this idea as long as it doesn't require much maintenance.  It
>> provides another stream of useful data to our redmine, so it really can
>> become THE central repo of info on project progress.
>>>>
>>>> .hc
>>>>
>>>> On Apr 12, 2013, at 1:35 PM, Abel Luck wrote:
>>>>
>>>>> Heya,
>>>>>
>>>>> So our desire to be full paranoid wrt the build server is of course
>>>>> justified, but conflicts up against our desire to be transparent in
>>>>> our processes as well.
>>>>>
>>>>> None of the info in Jenkins is confidential, it's just sensitive, we
>>>>> only want approved peeps to be able to edit it.
>>>>>
>>>>> There's no reason the info couldn't be exposed to the world read-only.
>>>>>
>>>>> Of course we don't want to expose the secure Jenkins publicly as that
>> is
>>>>> a huge attack surface.
>>>>>
>>>>> However, there is a plugin called Build Publisher Plugin
>>>>>
>>>>> "This plugin allows records from one Jenkins to be published on another
>>>>> Jenkins. The typical use case is for you to run builds within the
>>>>> firewall, then send the results to another Jenkins which is facing the
>>>>> outside world. "
>>>>>
>>>>> Proposal:
>>>>> We run a public jenkins instance on the dev.gp.i box, that slurps up
>>>>> data from the private secure jenkins.
>>>>>
>>>>> We could then also integrate jenkins with redmine [2], which will make
>>>>> dev.guardianproject.info the foci of our development effors.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> ~abel
>>>>>
>>>>>
>>>>> [1]:
>> https://wiki.jenkins-ci.org/display/JENKINS/Build+Publisher+Plugin
>>>>> [2]: http://www.r-labs.org/projects/r-labs/wiki/Hudson_En
>>>>> _______________________________________________
>>>>> Guardian-dev mailing list
>>>>>
>>>>> Post: Guardian-dev at lists.mayfirst.org
>>>>> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
>>>>>
>>>>> To Unsubscribe
>>>>>        Send email to:  Guardian-dev-unsubscribe at lists.mayfirst.org
>>>>>        Or visit:
>> https://lists.mayfirst.org/mailman/options/guardian-dev/hans%40guardianproject.info
>>>>>
>>>>> You are subscribed as: hans at guardianproject.info
>>>>
>>>
>> _______________________________________________
>> Guardian-dev mailing list
>>
>> Post: Guardian-dev at lists.mayfirst.org
>> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
>>
>> To Unsubscribe
>>         Send email to:  Guardian-dev-unsubscribe at lists.mayfirst.org
>>         Or visit:
>> https://lists.mayfirst.org/mailman/options/guardian-dev/mark%40guardianproject.info
>>
>> You are subscribed as: mark at guardianproject.info
>>
>