Internal hosting for Jenkins for short-term [RFC]

[Karsten 'quaid' Wade]

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

On 05/07/2012 08:28 PM, Itamar Heim wrote:

>> 
>> 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.
> 
> as stated above - we are looking at this as well.

OK, so far this discussion has been you and I agreeing on how to do
things, with no other objections. Unless there is an objection now :)
I'm going to say our +1s resolve the question in this thread.

Go ahead and run Jenkins slaves internally, etc., and just report back
out to this list (and write up on the wiki) as things are figured out
and enacted. Does that work for you?

- - 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/

iD8DBQFPqJyt2ZIOBq0ODEERAgr6AJ9G54f9OiIW7GdArZZ/Gh239+fehwCgvroW
firVYtUF3uCLYZCfAoaTOAE=
=4s/r
-----END PGP SIGNATURE-----