- Infra - oVirt List Archives

[JIRA] (OVIRT-682) Improve CI logging and reporting to Gerrit (v2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-682: ------------------------------- Summary: Improve CI logging and reporting to Gerrit (v2) (was: Improve CI logging) > Improve CI logging and reporting to Gerrit (v2) > ----------------------------------------------- > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: eedri > Assignee: infra > Priority: Low > Labels: standard-ci > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201608111129.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1523?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1523: ------------------------------------- One quick and dirty way to achieve this that was suggested by [~nsoffer(a)redhat.com] and made possible by [Gerrit 79316|https://gerrit.ovirt.org/#/c/79316/] is to create "fake distributions" such as "el7:a" and "el7:b". This will allow people to use YAML to make jobs that target those fake distributions. Making such "fake distributions" is actually quite easy in practice since we got [Gerrit 73690|https://gerrit.ovirt.org/#/c/73690/] > Support multipile executors per CI stage (V2) > --------------------------------------------- > > Key: OVIRT-1523 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. > It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. > Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

Barak Korren created OVIRT-1523: ----------------------------------- Summary: Support multipile executors per CI stage (V2) Key: OVIRT-1523 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1523) Support multipile executors per CI stage (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1523?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1523: -------------------------------- Epic Link: OVIRT-400 > Support multipile executors per CI stage (V2) > --------------------------------------------- > > Key: OVIRT-1523 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1523 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Currently we allow creating just one Jenkins "Free-Style" job per standard-CI stage and distribution. This means for e.g. that you can only have one "check-patch" script running on EL7 for a given project. > It had been requested several times to allow having multiple standard-CI scripts running in parallel on separate slaves as a means to get CI results faster. > Implementing this properly will probably require implementing both OVIRT-1522 and OVIRT-1013 -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1522) Re-implement standard-CI with pipelines (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1522?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1522: -------------------------------- Epic Link: OVIRT-400 > Re-implement standard-CI with pipelines (V2) > -------------------------------------------- > > Key: OVIRT-1522 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1522 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The Standard-CI system job in Jenkins are currently implemented using "Free-Style" Jenkins jobs, if we could re-implement them with Jenkins pipelines, if will enable us to use cleaner code and also have many features that may be to hard to implement with "Free-Style" jobs. > Tickets that specify features that will probably require using pipelines will linkt to this ticket as a blocker. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1522) Re-implement standard-CI with pipelines (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

Barak Korren created OVIRT-1522: ----------------------------------- Summary: Re-implement standard-CI with pipelines (V2) Key: OVIRT-1522 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1522 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra The Standard-CI system job in Jenkins are currently implemented using "Free-Style" Jenkins jobs, if we could re-implement them with Jenkins pipelines, if will enable us to use cleaner code and also have many features that may be to hard to implement with "Free-Style" jobs. Tickets that specify features that will probably require using pipelines will linkt to this ticket as a blocker. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation (V2)
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Summary: Automate standard-CI job creation (V2) (was: Automate standard-CI job creation) > Automate standard-CI job creation (V2) > -------------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1143: -------------------------------- Status: To Do (was: In Progress) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by eedri (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] eedri updated OVIRT-1143: ------------------------- Fix Version/s: (was: OVIRT-INFRA-FEB-2017) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by Barak Korren (oVirt JIRA) 12 Jul '17

12 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] Barak Korren reopened OVIRT-1143: --------------------------------- > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > Fix For: OVIRT-INFRA-FEB-2017 > > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

1 0