[ovirt-devel] Re: oci: command line tool for oVirt CI
Great idea, will try to contribute in my spare time.
Marcin
On 3/15/19 11:51 PM, Nir Soffer wrote:
I want to share a nice little tool that can make your life easier.
https://github.com/nirs/oci
With this PR:
https://github.com/nirs/oci/pull/1
You will be able to do this:
$ python system-tests.py 98535
2019-03-15 21:17:04,579 INFO [system-tests] [ 1/8 ] Getting build
info for change 98535
2019-03-15 21:17:05,295 INFO [system-tests] [ 2/8 ] Starting
build-artifacts job for {'url': u'git://gerrit.ovirt.org/vdsm
', 'ref': u'refs/changes/35/98535/3'}
2019-03-15 21:17:06,134 INFO [system-tests] [ 3/8 ] Waiting for
queue item https://jenkins.ovirt.org/queue/item/382806/
2019-03-15 21:17:07,960 INFO [system-tests] [ 4/8 ] Waiting for job
http://jenkins.ovirt.org/job/standard-manual-runner/89/
2019-03-15 21:26:21,381 INFO [system-tests] [ 5/8 ] Starting oVirt
system tests basic suite with custom repos
http://jenkins.ovirt.org/job/standard-manual-runner/89/
2019-03-15 21:26:22,242 INFO [system-tests] [ 6/8 ] Waiting for
queue item https://jenkins.ovirt.org/queue/item/382817/
2019-03-15 21:30:43,558 INFO [system-tests] [ 7/8 ] Waiting for job
http://jenkins.ovirt.org/job/ovirt-system-tests_manual/4330/
2019-03-15 22:10:52,891 INFO [system-tests] [ 8/8 ] System tests
completed with SUCCESS
Yes, one command from your favorite shell. It takes about 53 minutes,
but on Fedora you get
notifications when commands finish.
No need to to add "ci please build" comment, wait until the job is
complete, copy the job url, open OST page,
wait (jenkins is slow), paste the build artifacts url, start the job,
wait, wait more, check if OST is done, (not yet),
wait more..., OST finished, check the logs, did you paste the wrong url?
The tool is not finished yet. If you like to contribute to this fun
little project please check
the issues:
https://github.com/nirs/oci/issues
Most of the issues are easy. Some harder like:
- https://github.com/nirs/oci/issues/11
- https://github.com/nirs/oci/issues/12
Feel free to open new issues if you have an idea for this tool.
Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/UBEAPFMUJMNPW3PU3FRPLRPOXWDIKWMA/
[ovirt-devel] Re: oci: command line tool for oVirt CI
On Mon, Mar 18, 2019 at 11:13 AM Eyal Edri wrote:
>
>
> On Sat, Mar 16, 2019 at 12:52 AM Nir Soffer wrote:
>
>> I want to share a nice little tool that can make your life easier.
>> https://github.com/nirs/oci
>>
>> With this PR:
>> https://github.com/nirs/oci/pull/1
>>
>> You will be able to do this:
>>
>> $ python system-tests.py 98535
>> 2019-03-15 21:17:04,579 INFO[system-tests] [ 1/8 ] Getting build info
>> for change 98535
>> 2019-03-15 21:17:05,295 INFO[system-tests] [ 2/8 ] Starting
>> build-artifacts job for {'url': u'git://gerrit.ovirt.org/vdsm', 'ref':
>> u'refs/changes/35/98535/3'}
>> 2019-03-15 21:17:06,134 INFO[system-tests] [ 3/8 ] Waiting for queue
>> item https://jenkins.ovirt.org/queue/item/382806/
>> 2019-03-15 21:17:07,960 INFO[system-tests] [ 4/8 ] Waiting for job
>> http://jenkins.ovirt.org/job/standard-manual-runner/89/
>> 2019-03-15 21:26:21,381 INFO[system-tests] [ 5/8 ] Starting oVirt
>> system tests basic suite with custom repos
>> http://jenkins.ovirt.org/job/standard-manual-runner/89/
>> 2019-03-15 21:26:22,242 INFO[system-tests] [ 6/8 ] Waiting for queue
>> item https://jenkins.ovirt.org/queue/item/382817/
>> 2019-03-15 21:30:43,558 INFO[system-tests] [ 7/8 ] Waiting for job
>> http://jenkins.ovirt.org/job/ovirt-system-tests_manual/4330/
>> 2019-03-15 22:10:52,891 INFO[system-tests] [ 8/8 ] System tests
>> completed with SUCCESS
>>
>> Yes, one command from your favorite shell. It takes about 53 minutes, but
>> on Fedora you get
>> notifications when commands finish.
>>
>> No need to to add "ci please build" comment, wait until the job is
>> complete, copy the job url, open OST page,
>> wait (jenkins is slow), paste the build artifacts url, start the job,
>> wait, wait more, check if OST is done, (not yet),
>> wait more..., OST finished, check the logs, did you paste the wrong url?
>>
>> The tool is not finished yet. If you like to contribute to this fun
>> little project please check
>> the issues:
>> https://github.com/nirs/oci/issues
>>
>> Most of the issues are easy. Some harder like:
>> - https://github.com/nirs/oci/issues/11
>> - https://github.com/nirs/oci/issues/12
>>
>> Feel free to open new issues if you have an idea for this tool.
>>
>
> Thanks for contributing for the oVirt CI ecosystem!
> You might want to add params to the CLI to choose which suites you're
> running ( master/4.3/4.2 )?
> I guess it takes the default master for now?
>
Also,
Going forward if we're going to have more scripts and tools contributed by
the community, we might want to have
and official GitHub repo under the oVirt Org that will hold them ( and also
enjoy CI on it own...)
>
>
>>
>> Nir
>>
>> ___
>> Devel mailing list -- devel@ovirt.org
>> To unsubscribe send an email to devel-le...@ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
>> https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/GU4SE5DGZ3UW4KUK4GL7V55R3RWZKAVB/
>>
>
>
> --
>
> Eyal edri
>
>
> MANAGER
>
> RHV/CNV DevOps
>
> EMEA VIRTUALIZATION R
>
>
> Red Hat EMEA TRIED. TESTED. TRUSTED.
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>
--
Eyal edri
MANAGER
RHV/CNV DevOps
EMEA VIRTUALIZATION R
Red Hat EMEA TRIED. TESTED. TRUSTED.
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/KHQ6M76WYSAUIDSO6NKI6IC2OWUE6CQU/
[ovirt-devel] Re: oci: command line tool for oVirt CI
On Sat, Mar 16, 2019 at 12:52 AM Nir Soffer wrote:
> I want to share a nice little tool that can make your life easier.
> https://github.com/nirs/oci
>
> With this PR:
> https://github.com/nirs/oci/pull/1
>
> You will be able to do this:
>
> $ python system-tests.py 98535
> 2019-03-15 21:17:04,579 INFO[system-tests] [ 1/8 ] Getting build info
> for change 98535
> 2019-03-15 21:17:05,295 INFO[system-tests] [ 2/8 ] Starting
> build-artifacts job for {'url': u'git://gerrit.ovirt.org/vdsm', 'ref':
> u'refs/changes/35/98535/3'}
> 2019-03-15 21:17:06,134 INFO[system-tests] [ 3/8 ] Waiting for queue
> item https://jenkins.ovirt.org/queue/item/382806/
> 2019-03-15 21:17:07,960 INFO[system-tests] [ 4/8 ] Waiting for job
> http://jenkins.ovirt.org/job/standard-manual-runner/89/
> 2019-03-15 21:26:21,381 INFO[system-tests] [ 5/8 ] Starting oVirt
> system tests basic suite with custom repos
> http://jenkins.ovirt.org/job/standard-manual-runner/89/
> 2019-03-15 21:26:22,242 INFO[system-tests] [ 6/8 ] Waiting for queue
> item https://jenkins.ovirt.org/queue/item/382817/
> 2019-03-15 21:30:43,558 INFO[system-tests] [ 7/8 ] Waiting for job
> http://jenkins.ovirt.org/job/ovirt-system-tests_manual/4330/
> 2019-03-15 22:10:52,891 INFO[system-tests] [ 8/8 ] System tests
> completed with SUCCESS
>
> Yes, one command from your favorite shell. It takes about 53 minutes, but
> on Fedora you get
> notifications when commands finish.
>
> No need to to add "ci please build" comment, wait until the job is
> complete, copy the job url, open OST page,
> wait (jenkins is slow), paste the build artifacts url, start the job,
> wait, wait more, check if OST is done, (not yet),
> wait more..., OST finished, check the logs, did you paste the wrong url?
>
> The tool is not finished yet. If you like to contribute to this fun little
> project please check
> the issues:
> https://github.com/nirs/oci/issues
>
> Most of the issues are easy. Some harder like:
> - https://github.com/nirs/oci/issues/11
> - https://github.com/nirs/oci/issues/12
>
> Feel free to open new issues if you have an idea for this tool.
>
Thanks for contributing for the oVirt CI ecosystem!
You might want to add params to the CLI to choose which suites you're
running ( master/4.3/4.2 )?
I guess it takes the default master for now?
>
> Nir
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/GU4SE5DGZ3UW4KUK4GL7V55R3RWZKAVB/
>
--
Eyal edri
MANAGER
RHV/CNV DevOps
EMEA VIRTUALIZATION R
Red Hat EMEA TRIED. TESTED. TRUSTED.
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/BRLLDBWDMPTQWNQB75EBVPCTOW2LSZCC/
[ovirt-devel] Re: oci: command line tool for oVirt CI
On 3/15/19 11:51 PM, Nir Soffer wrote: I want to share a nice little tool that can make your life easier. https://github.com/nirs/oci VERY nice! kudos! -- Francesco Romani Senior SW Eng., Virtualization R Red Hat IRC: fromani github: @fromanirh ___ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/FPTWT6EHS5CVSIZQRVJ6ABJAZAAU74GJ/
[ovirt-devel] Re: oci: command line tool for oVirt CI
±1
On Sat 16 Mar, 2019, 4:22 AM Nir Soffer, wrote:
> I want to share a nice little tool that can make your life easier.
> https://github.com/nirs/oci
>
> With this PR:
> https://github.com/nirs/oci/pull/1
>
> You will be able to do this:
>
> $ python system-tests.py 98535
> 2019-03-15 21:17:04,579 INFO[system-tests] [ 1/8 ] Getting build info
> for change 98535
> 2019-03-15 21:17:05,295 INFO[system-tests] [ 2/8 ] Starting
> build-artifacts job for {'url': u'git://gerrit.ovirt.org/vdsm', 'ref':
> u'refs/changes/35/98535/3'}
> 2019-03-15 21:17:06,134 INFO[system-tests] [ 3/8 ] Waiting for queue
> item https://jenkins.ovirt.org/queue/item/382806/
> 2019-03-15 21:17:07,960 INFO[system-tests] [ 4/8 ] Waiting for job
> http://jenkins.ovirt.org/job/standard-manual-runner/89/
> 2019-03-15 21:26:21,381 INFO[system-tests] [ 5/8 ] Starting oVirt
> system tests basic suite with custom repos
> http://jenkins.ovirt.org/job/standard-manual-runner/89/
> 2019-03-15 21:26:22,242 INFO[system-tests] [ 6/8 ] Waiting for queue
> item https://jenkins.ovirt.org/queue/item/382817/
> 2019-03-15 21:30:43,558 INFO[system-tests] [ 7/8 ] Waiting for job
> http://jenkins.ovirt.org/job/ovirt-system-tests_manual/4330/
> 2019-03-15 22:10:52,891 INFO[system-tests] [ 8/8 ] System tests
> completed with SUCCESS
>
> Yes, one command from your favorite shell. It takes about 53 minutes, but
> on Fedora you get
> notifications when commands finish.
>
> No need to to add "ci please build" comment, wait until the job is
> complete, copy the job url, open OST page,
> wait (jenkins is slow), paste the build artifacts url, start the job,
> wait, wait more, check if OST is done, (not yet),
> wait more..., OST finished, check the logs, did you paste the wrong url?
>
> The tool is not finished yet. If you like to contribute to this fun little
> project please check
> the issues:
> https://github.com/nirs/oci/issues
>
> Most of the issues are easy. Some harder like:
> - https://github.com/nirs/oci/issues/11
> - https://github.com/nirs/oci/issues/12
>
> Feel free to open new issues if you have an idea for this tool.
>
> Nir
>
> ___
> Devel mailing list -- devel@ovirt.org
> To unsubscribe send an email to devel-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/GU4SE5DGZ3UW4KUK4GL7V55R3RWZKAVB/
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/XYCDPGKHDFDW5B3F7NY42ZZBEAUVKBGP/
