- Infra - oVirt List Archives

[JIRA] (OVIRT-1197) Re-factor the standard-CI publishers file
by Barak Korren (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1197?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1197: -------------------------------- Labels: standard-ci (was: ) > Re-factor the standard-CI publishers file > ----------------------------------------- > > Key: OVIRT-1197 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1197 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Thi has already been improved as part of OVIRT-988 (in [Gerrit 69194|https://gerrit.ovirt.org/#/c/69194] But there is more work to do. > We can probably have the same publishers macro for all Standard-CI jobs, and add conditional steps to: > # Collect test results if any > # Improve output to Gerrit > # Launch deploy-to-experimental if this is a build-artifacts job and the patch was merged > This way we can finally stop having to have a separate entry for the build-artifacts jobs and simplify the project YAML files. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1157) Re-factor the standard-CI triggers file
by Barak Korren (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1157?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1157 at 2/26/17 12:31 PM: --------------------------------------------------------------- Before re-factoring we should probably remove trigger customization from the project YAML files, this is probably shouldn't be allowed anyway and perhaps not even used much. This allong with OVIRT-1197 may allow us to merge the build-artifacts and build-artifacts-on-demand jobs together. was (Author: bkorren(a)redhat.com) Before re-factoring we should probably remove trigger customization from the project YAML files, this is probably shouldn't be allowed anyway and perhaps not even used much. This may allow us to merge the build-artifacts and build-artifacts-on-demand jobs together. > Re-factor the standard-CI triggers file > --------------------------------------- > > Key: OVIRT-1157 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1157 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The {{/jobs/confs/yaml/triggers/standard.yaml}} file contains A LOT of needless code duplication. We need to re-factor it with templates and YAML inheritance. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1197) Re-factor the standard-CI publishers file
by Barak Korren (oVirt JIRA) 26 Feb '17

26 Feb '17

Barak Korren created OVIRT-1197: ----------------------------------- Summary: Re-factor the standard-CI publishers file Key: OVIRT-1197 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1197 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Thi has already been improved as part of OVIRT-988 (in [Gerrit 69194|https://gerrit.ovirt.org/#/c/69194] But there is more work to do. We can probably have the same publishers macro for all Standard-CI jobs, and add conditional steps to: # Collect test results if any # Improve output to Gerrit # Launch deploy-to-experimental if this is a build-artifacts job and the patch was merged This way we can finally stop having to have a separate entry for the build-artifacts jobs and simplify the project YAML files. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1197) Re-factor the standard-CI publishers file
by Barak Korren (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1197?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1197: -------------------------------- Epic Link: OVIRT-400 > Re-factor the standard-CI publishers file > ----------------------------------------- > > Key: OVIRT-1197 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1197 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Thi has already been improved as part of OVIRT-988 (in [Gerrit 69194|https://gerrit.ovirt.org/#/c/69194] But there is more work to do. > We can probably have the same publishers macro for all Standard-CI jobs, and add conditional steps to: > # Collect test results if any > # Improve output to Gerrit > # Launch deploy-to-experimental if this is a build-artifacts job and the patch was merged > This way we can finally stop having to have a separate entry for the build-artifacts jobs and simplify the project YAML files. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1157) Re-factor the standard-CI triggers file
by Barak Korren (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1157?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1157 at 2/26/17 12:14 PM: --------------------------------------------------------------- Before re-factoring we should probably remove trigger customization from the project YAML files, this is probably shouldn't be allowed anyway and perhaps not even used much. This may allow us to merge the build-artifacts and build-artifacts-on-demand jobs together. was (Author: bkorren(a)redhat.com) Before re-factoring we should probably remove trigger customization from the project YAML files, this is probably shouldn't be allowed anyway and perhaps not even used much. This may allow us to merge the build-artifacts and build-artifacts on demand jobs together. > Re-factor the standard-CI triggers file > --------------------------------------- > > Key: OVIRT-1157 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1157 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The {{/jobs/confs/yaml/triggers/standard.yaml}} file contains A LOT of needless code duplication. We need to re-factor it with templates and YAML inheritance. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1157) Re-factor the standard-CI triggers file
by Barak Korren (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1157?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1157: ------------------------------------- Before re-factoring we should probably remove trigger customization from the project YAML files, this is probably shouldn't be allowed anyway and perhaps not even used much. This may allow us to merge the build-artifacts and build-artifacts on demand jobs together. > Re-factor the standard-CI triggers file > --------------------------------------- > > Key: OVIRT-1157 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1157 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The {{/jobs/confs/yaml/triggers/standard.yaml}} file contains A LOT of needless code duplication. We need to re-factor it with templates and YAML inheritance. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1157) Re-factor the standard-CI triggers file
by Barak Korren (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1157?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1157: -------------------------------- Labels: standard-ci (was: ) > Re-factor the standard-CI triggers file > --------------------------------------- > > Key: OVIRT-1157 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1157 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The {{/jobs/confs/yaml/triggers/standard.yaml}} file contains A LOT of needless code duplication. We need to re-factor it with templates and YAML inheritance. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-682) Improve CI logging
by Barak Korren (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] Barak Korren edited comment on OVIRT-682 at 2/26/17 11:58 AM: -------------------------------------------------------------- We can probably improve the user experience by putting a better message in Gerrit, something like: {quote} You can see standard-CI script output log +here(1)+ For individual test results please +click here(2)+, or use the +test results analyser(3)+ Additional built artifacts can be found +here(4)+ For full, unfiltered, job output +click here(5)+ To re-trigger the job +click here(6)+ or type *\@ci check* {quote} Where: * (1) points to the {{check-patch.sh}}, {check-merged.sh}}, etc. script output. * If any JUNIT XML files were found (If not the line shouldnt be shown): ** (2) points to the test results page ** (3) point to the test results analyser * If any artifacts that are not mock logs or JUNIT XML files wee found (4) points to them. If <= 3 artifacts found we may even include direct links (This will be useful for things like {{differences.html}} in the Jenkins repo. * (5) Will point to the good-old job console output screen * If the job failed, (6) will point to the re-trigger button We will need to check if its possible to embed links in Gerrit comments. If no we will unfortunately have to use ugly full URLs. was (Author: bkorren(a)redhat.com) We can probably improve the user experience by putting a better message in Gerrit, something like: {quote} You can see standard-CI script output log +here(1)+ For individual test results please +click here(2)+, or use the +test results analyser(3)+ Additional built artifacts can be found +here(4)+ For full, unfiltered, job output +click here(5)+ {quote} Where: * (1) points to the {{check-patch.sh}}, {check-merged.sh}}, etc. script output. * If any JUNIT XML files were found (If not the line shouldnt be shown): ** (2) points to the test results page ** (3) point to the test results analyser * If any artifacts that are not mock logs or JUNIT XML files wee found (4) points to them. If <= 3 artifacts found we may even include direct links (This will be useful for things like {{differences.html}} in the Jenkins repo. * (5) Will point to the good-old job console output screen We will need to check if its possible to embed links in Gerrit comments. If no we will unfortunately have to use ugly full URLs. > Improve CI logging > ------------------ > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > 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.784.2#100032)

1 0

[JIRA] (OVIRT-682) Improve CI logging
by Barak Korren (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-682: ------------------------------------ We can probably improve the user experience by putting a better message in Gerrit, something like: {quote} You can see standard-CI script output log +here(1)+ For individual test results please +click here(2)+, or use the +test results analyser(3)+ Additional built artifacts can be found +here(4)+ For full, unfiltered, job output +click here(5)+ {quote} Where: * (1) points to the {{check-patch.sh}}, {check-merged.sh}}, etc. script output. * If any JUNIT XML files were found (If not the line shouldnt be shown): ** (2) points to the test results page ** (3) point to the test results analyser * If any artifacts that are not mock logs or JUNIT XML files wee found (4) points to them. If <= 3 artifacts found we may even include direct links (This will be useful for things like {{differences.html}} in the Jenkins repo. * (5) Will point to the good-old job console output screen We will need to check if its possible to embed links in Gerrit comments. If no we will unfortunately have to use ugly full URLs. > Improve CI logging > ------------------ > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: infra > > 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.784.2#100032)

1 0

Clone job failing although all criteria is met
by Tal Nisan 26 Feb '17

26 Feb '17

Trying to clone this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1418280 With the new clone job fails on a missing flag although all flags exist: https://rhev-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/bugzilla_clone_bug…

1 0