Internal hosting for Jenkins for short-term [RFC]

[Karsten 'quaid' Wade]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/23/2012 11:33 PM, Itamar Heim wrote:

>> my view is until we can resolve how to do this over publicly
>> accessible community resources via some hosting provider, private
>> CI is better to no CI.

Itamar and I have been having some progress internally on getting
hosts that may be able to be exposed externally so we can have shared
community infrastructure.

Based on that and the immediate need, I'd like us to start allowing
Itamar's team to use whatever they have internally to support
development, with these understandings:

* Publish all results ASAP publicly, as per usual.
* Move the workloads externally ASAP when we can.
* Look for the future of how we want to handle enabling Jenkins
servers to be used on internal networks so oVirt members can use more
readily available internal hosts for infrastructure that doesn't
require or benefit from an open collaboration.

Basically, it makes sense to me that if we have a standard set of
workloads that can be run on any instance, there is no reason anyone
can't commit to doing that on infrastructure they run themselves. That
is different from the actual participation components that should be
run entirely externally. The project needs to have 100% r/w access to
all of the online components that make up the project, but that
doesn't have to include CI servers running a standard workload on an
open source stack.

- - Karsten
- -- 
name:  Karsten 'quaid' Wade, Sr. Community Architect
team:    Red Hat Community Architecture & Leadership
uri:              http://communityleadershipteam.org
                         http://TheOpenSourceWay.org
gpg:                                        AD0E0C41
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFPqC4X2ZIOBq0ODEERAqTgAKCJx6k7c06qp/lUO+5l35o6SiH4nwCglkRr
i9CJLIXQwAMnPK92H9V0mF8=
=eq3m
-----END PGP SIGNATURE-----