[JIRA] (OVIRT-2657) Please import ovirt-engine-sdk-go in oVirt
organization
by sbonazzo (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2657?page=com.atlassian.jir... ]
sbonazzo commented on OVIRT-2657:
---------------------------------
Il giorno ven 25 gen 2019 alle ore 06:00 Joey Ma <majunjiev(a)gmail.com> ha
scritto:
> Hi Sandro,
>
> I'm writing to expect to have a discussion with you about the upcoming CI
> integration work.
>
> As we know that the ovirt-engine-sdk-go project is just a generator for go
> sdk, not the sdk itself. So previously I used Travis-CI [1] to do the
> testing and building, as well as pushing the auto-generated sdk code back
> to another github repo https://github.com/imjoey/go-ovirt . Developers
> could then use the sdk easily by '''import "github.com/imjoey/go-ovirt"
> '''.
>
> So I was wondering if the CI integration work could be divided into the
> following sequenced steps:
> 1. Transfer the existing imjoey/go-ovirt repo under oVirt org, as also
> mentioned in [2];
> 2. Besides the testing and building by Travis-CI, also make the
> ovirt/ovirt-engine-sdk-go repo be capable of pushing the auto-generated
> code to the ovirt/go-ovirt repo;
> > Much similar to that the kubevirt/kubevirt project uses Travis-CI to
> push the auto-generated Python SDK back to kubevirt/client-python [3];
> 3. Add integration with oVirt jenkins for testing, building and packaging
> for rpm/src-rpm;
>
> To be honest, I am not quite sure if that meets the standard in our
> community. Please feel free to correct me and your insights on that would
> be highly appreciated. Thanks.
>
>
Ondra can you please assist Joey setting up automation for the Go SDK to
match the other SDKs?
> Regards,
> Joey
>
> [1]: *https://github.com/oVirt/ovirt-engine-sdk-go/blob/master/.travis/deploy-codes.sh
> <https://github.com/oVirt/ovirt-engine-sdk-go/blob/master/.travis/deploy-c...>*
> [2]: https://ovirt-jira.atlassian.net/browse/OVIRT-2460
> [3]: https://github.com/kubevirt/client-python
>
> On Mon, Jan 21, 2019 at 3:58 PM Sandro Bonazzola <sbonazzo(a)redhat.com>
> wrote:
>
>> Hi,
>> ovirt-engine-sdk-go project has been accepted as incubator project under
>> oVirt organization.
>> Can you please import it granting Joey Ma <majunjiev(a)gmail.com>
>> maintainer privileges for it? Joey has been already added as developer to
>> oVirt team in github with
>> https://ovirt-jira.atlassian.net/browse/OVIRT-2460
>> The project is currently in github at
>> https://github.com/imjoey/ovirt-engine-sdk-go
>>
>> Joey, once the project is imported, please ensure to create jenkins jobs
>> for testing and building it and add builds to master and 4.3 change queues.
>>
>> Thanks,
>> --
>>
>> SANDRO BONAZZOLA
>>
>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
>>
>> Red Hat EMEA <https://www.redhat.com/>
>>
>> sbonazzo(a)redhat.com
>> <https://red.ht/sig>
>>
>
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>
> Please import ovirt-engine-sdk-go in oVirt organization
> -------------------------------------------------------
>
> Key: OVIRT-2657
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2657
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: sbonazzo
> Assignee: infra
>
> Hi,
> ovirt-engine-sdk-go project has been accepted as incubator project under
> oVirt organization.
> Can you please import it granting Joey Ma <majunjiev(a)gmail.com> maintainer
> privileges for it? Joey has been already added as developer to oVirt team
> in github with https://ovirt-jira.atlassian.net/browse/OVIRT-2460
> The project is currently in github at
> https://github.com/imjoey/ovirt-engine-sdk-go
> Joey, once the project is imported, please ensure to create jenkins jobs
> for testing and building it and add builds to master and 4.3 change queues.
> Thanks,
> --
> SANDRO BONAZZOLA
> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
> Red Hat EMEA <https://www.redhat.com/>
> sbonazzo(a)redhat.com
> <https://red.ht/sig>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100098)
5 years, 10 months