hi guys,
I believe we are fairly well established on the ci.centos.org infra to now consider moving the ci.dev instances from their present location at godaddy.com.
This would also allow us to run the ci.dev nightly tests on baremetal machines.
It would also allow us to consolidate the jenkins instance, and maybe SIGs and other tested projects could use the distro runs as a trigger for their own validation / testing.
Brian, can we find a slot in one of the CBS meetings to work through this ?
Regards,
On Jun 03 04:20, Karanbir Singh wrote:
hi guys,
I believe we are fairly well established on the ci.centos.org infra to now consider moving the ci.dev instances from their present location at godaddy.com.
This would also allow us to run the ci.dev nightly tests on baremetal machines.
It would also allow us to consolidate the jenkins instance, and maybe SIGs and other tested projects could use the distro runs as a trigger for their own validation / testing.
Brian, can we find a slot in one of the CBS meetings to work through this ?
Sure! I've added this to the agenda for Monday (08-June).
Regards,
-- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
--Brian
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/06/15 05:20, Karanbir Singh wrote:
hi guys,
I believe we are fairly well established on the ci.centos.org infra to now consider moving the ci.dev instances from their present location at godaddy.com.
This would also allow us to run the ci.dev nightly tests on baremetal machines.
It would also allow us to consolidate the jenkins instance, and maybe SIGs and other tested projects could use the distro runs as a trigger for their own validation / testing.
Brian, can we find a slot in one of the CBS meetings to work through this ?
Regards,
Why not, the only thing to do is then import existing jobs (and converting this to use the duffy middleware to request a bare metal node, instead of deploying a virtual machine).
Can you elaborate on the "other tested projects could use the distro runs as trigger" ?
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 03/06/15 12:52, Fabian Arrotin wrote:
Can you elaborate on the "other tested projects could use the distro runs as trigger" ?
if other projects and tests want to trigger based on the result of the t_functional result they will be able to do that easier, if all the stack is in the same jenkins instance.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/06/15 13:03, Karanbir Singh wrote:
On 03/06/15 12:52, Fabian Arrotin wrote:
Can you elaborate on the "other tested projects could use the distro runs as trigger" ?
if other projects and tests want to trigger based on the result of the t_functional result they will be able to do that easier, if all the stack is in the same jenkins instance.
gotcha .. so chaining builds is really a cool feature if we "merge" those two jenkins instances ..
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
-
Brian Stinson -
Fabian Arrotin -
Karanbir Singh -
Karanbir Singh