On Tue, 19 Feb 2019 at 09:14, Joey Ma <majunjiev(a)gmail.com> wrote:
Hi all,
Hi Joey,
With the generous help of several nice guys, currently the Go SDK related
projects, oVirt/ovirt-engine-sdk-go and oVirt/go-ovirt, are already
available under oVirt org, and the integration of oVirt/ovirt-engine-sdk-go
with oVirt STD-CI is also completed [1]. Sincerely thank you to everyone.
While there is still an issue left that we need a proper solution to
integrate oVirt/ovirt-engine-sdk-go with TravisCI which could push the
auto-generated codes into oVirt/go-ovirt. Previously I adopted my
personal github access token which is stored encrypted [2] to work it out.
But as it's been under oVirt community, we need a more regular way to make
this. As @Evgheni <ederevea(a)redhat.com> suggested, maybe a new access
token from a dedicated github account or via the Jenkins job will work?
Any one could help? Any insights into this would be appreciated and thanks
in advance.
If you do it from the STDCI script (The Jenkin job), we could make the
credentials for the STDCI GitHub bot available to the script when it runs
(See the section about secrets in the standard CI docs
<
https://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_stand...
for a full explanation about how this works).
I`d want do understand how the flow works and what is its purpose, it
sounds to me a bit strange that we need to push from one repo to the other.
Regards,
Barak.
--
Barak Korren
RHV DevOps team , RHCE, RHCi
Red Hat EMEA
redhat.com | TRIED. TESTED. TRUSTED. |
redhat.com/trusted