On 06/08/2015 10:24 PM, Karsten Wade wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 06/08/2015 09:23 AM, Jan Chaloupka wrote: >> What about I will first test the new or updated job for CentOS in >> internal env and then forward all changes to someone responsible >> for CentOS's CI which would be who? I am not against taking care of >> this part if I get an access/credentials to CentOS to access your >> CI. > I'll let others speak up about this, but if I'm reading you correctly, > the above is what we are looking for -- upstream project teams willing > and able to "own" their jobs in ci.centos.org. There really aren't > many spare resources (people's time) waiting to take jobs thrown over > a wall and own them for you. > > You would join the Atomic SIG and ask for credentials to build and run > CI jobs for all of the above. In fact, you are probably welcome to > move all your jobs to ci.centos.org as your single place to work from > rather than the internal-to-RH CI. How can join the Atomic SIG? Is there a workflow for it I have to follow? Still I would like to be a mediator that would "just" update jobs in ci.centos.org and left analysis of errors/fails for one who is responsible for given component in CentOS. Kubernets Navid, Docker and etcd Lokesh, ... > Regards, > - - Karsten > - -- > Karsten 'quaid' Wade .^\ CentOS Doer of Stuff > http://TheOpenSourceWay.org \ http://community.redhat.com > @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iEYEARECAAYFAlV1+eQACgkQ2ZIOBq0ODEGBGgCgo6VqxyUwu0XDWumQwZpO6gaz > 54YAn1TvuENm0iNa3WAnC6xdGJZj/mdQ > =oPRg > -----END PGP SIGNATURE----- > _______________________________________________ > CentOS-devel mailing list > CentOS-devel at centos.org > http://lists.centos.org/mailman/listinfo/centos-devel