I think it is fine to use your own account if you're listening only to the 
gerrit event stream for debug puprposes.
If you wanted your CI system to have its own ssh keys or post comments on 
patches, then you'd want a dedicated ci account for that using these 
instructions [1]
Ramy

[1] 
http://docs.openstack.org/infra/system-config/third_party.html#creating-a-service-account


-----Original Message-----
From: Anton Khaldin [mailto:[email protected]] 
Sent: Tuesday, October 06, 2015 11:38 AM
To: OpenStack Infra <[email protected]>
Cc: Anton Khaldin <[email protected]>
Subject: [OpenStack-Infra] Account for internal CICD system

Hi everyone
I'm working on internal version of CICD automation for OpenStack last two 
months and I have few questions.

But first of all I would like say "Great thanks" for everyone how is working on 
openstack-infra, anyone who maintain, develop, test and orginize community 
CICD. All this work looks very cool and so great.
I've replicated only part of community cicd automation : systems/tools (zuul, 
nodepool, diskiamge-builder,jenkins-job-builder,...) and configuration (sync it 
periodically). Main goals of internal replicate of community cicd are support 
internal developers and simplify life of siteops (upgrade, rollback, check 
compatibility), I hope it can be usefull for community.


At this moment I'm using my account (akhaldin, 
https://launchpad.net/~anton-haldin ) to get events from review.openstack.org. 
Am I right that it would be better to create special non-personal account for 
our internal CICD ? I'm sorry if I've missed some usefull links/docuemnts which 
are describing vision on how internal CICD system can be integrated with 
community CICD. Before this moment I was working primarly with technical issue 
(network limitation, corporate policies, testing changes in configuration) and 
only after technical part is done I can think about important org questions.



Best regards,
Anton Haldin.


_______________________________________________
OpenStack-Infra mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

_______________________________________________
OpenStack-Infra mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra

Reply via email to