- Infra - oVirt List Archives

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1732: -------------------------------- Issue Type: Improvement (was: Bug) Priority: Medium (was: High) > Make 'poll-upstream-chages' job abandon old changes it made > ----------------------------------------------------------- > > Key: OVIRT-1732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, standard-ci > > The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest. > The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually. > We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1732: -------------------------------- Component/s: (was: oVirt CI) pusher.py > Make 'poll-upstream-chages' job abandon old changes it made > ----------------------------------------------------------- > > Key: OVIRT-1732 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: pusher.py > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: poll-upstream-sources, standard-ci > > The poll-upstream-changes job creates patches when it runs. Not all these patches need or should be merged. When maintainers get around to looking at them, they typically can just merge the latest patch and throw away the rest. > The issue is that over time, the patches created by the job can accumulate, and it can be cumbersome for maintainers to remove un-needed ones manually. > We should make the poll job remove un-needed patches it made. It needs to look at the last SHA in the upstream-sources.yaml file, and remove all that patches that include an older SHA automatically. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1734: -------------------------------- Component/s: Standard CI (Freestyle) Staging infra CI client projects > Add CI jobs to test slaves on staging engine > -------------------------------------------- > > Key: OVIRT-1734 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1734 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI client projects, Jenkins Slaves, Staging infra, Standard CI (Freestyle) > Reporter: Barak Korren > Assignee: infra > Labels: staging > > After the staging engine was installed, several VMs were created on it and added as slaves to the staging Jenkins. > We need to add some jobs that will take advantage on those slaves so we can tell if they are working properly. > The should probably just add CI jobs for the 'jenkins' repo. That repo is already configured to run some jobs on the staging Jenkins and is mostly maintained by our team, so and issues there will be visible to us. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1734: -------------------------------- Component/s: (was: oVirt Infra) (was: oVirt CI) Jenkins Slaves > Add CI jobs to test slaves on staging engine > -------------------------------------------- > > Key: OVIRT-1734 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1734 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > Labels: staging > > After the staging engine was installed, several VMs were created on it and added as slaves to the staging Jenkins. > We need to add some jobs that will take advantage on those slaves so we can tell if they are working properly. > The should probably just add CI jobs for the 'jenkins' repo. That repo is already configured to run some jobs on the staging Jenkins and is mostly maintained by our team, so and issues there will be visible to us. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1739?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1739: -------------------------------- Component/s: (was: oVirt CI) STDCI DSL Standard CI (Pipelines) Standard CI (Freestyle) > Unified code owners mechanism between Gerrit and GitHub > ------------------------------------------------------- > > Key: OVIRT-1739 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git, GitHub, Standard CI (Freestyle), Standard CI (Pipelines), STDCI DSL > Reporter: Barak Korren > Assignee: infra > Labels: gerrit, github, reviewers, standard-ci > > "Code owners" is the mechanism that automatically assigns reviewers to new code patches. > In Gerrit we use the "reviewers" plugin to automatically set reviewers (See OVIRT-1165). > GitHub has its own mechanism: https://github.com/blog/2392-introducing-code-owners > We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Component/s: OST Manual job > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST Manual job, Standard CI (Freestyle) > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1743) ci please build and send to OST
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1743: -------------------------------- Component/s: (was: oVirt CI) Standard CI (Freestyle) > ci please build and send to OST > ------------------------------- > > Key: OVIRT-1743 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1743 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Freestyle) > Reporter: danken > Assignee: infra > Labels: change-queue > > Can you please automate the frequent process, which is slow and error prone? > I am writing a patch, and would like to test it in ost. now I need to > * "ci please build" > * copy el7 url > * wait for el7 build to finish > * copy artifacts url to ovirt--system-test-manual, start it > * copy the ost run URL to the gerrit patch, so I have it for reference of failure/success. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1745) Make upstream source collection and polling code usable for pipelines
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

This is a multi-part message in MIME format... ------------=_1515572840-15436-331 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1745: -------------------------------- Component/s: (was: oVirt CI) usrc.py pusher.py > Make upstream source collection and polling code usable for pipelines > --------------------------------------------------------------------- > > Key: OVIRT-1745 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: pusher.py, usrc.py > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, upstream-source-collector > > The upstream source collection and polling code is currently only suitable for use in Free-Style jobs. This is because: > # We support having 'jenkins' repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism to get the actual code from the main 'jenkins' repo in gerrit.ovirt.org > # This creates a situation where in order to get the STDCI code we need to run the upstream sources code > # This creates a chicken and and egg problem because the upstream sources code is part of the STDCI code > # To solve this issue we simply embedded the upstream sources code into the job code by using '{{#include}}' in JJB rather then running it as a stand-alone script. > # This technique is not usable for pipelines, so we need to come with a different solution and make the required adjustments to the source collection and polling code. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515572840-15436-331 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1745?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1745:</h3> <pre> Component/s: (was: oVirt CI) usrc.py pusher.py</pre> <blockquote><h3>Make upstream source collection and polling code usable for pipelines</h3> <pre> Key: OVIRT-1745 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1745 Project: oVirt - virtualization made easy Issue Type: New Feature Components: pusher.py, usrc.py Reporter: Barak Korren Assignee: infra Labels: poll-upstream-sources, upstream-source-collector</pre> <p>The upstream source collection and polling code is currently only suitable for use in Free-Style jobs. This is because: # We support having ‘jenkins’ repositories (Where jobs expect STDCI code to be found) use the upstream sources mechanism to get the actual code from the main ‘jenkins’ repo in gerrit.ovirt.org # This creates a situation where in order to get the STDCI code we need to run the upstream sources code # This creates a chicken and and egg problem because the upstream sources code is part of the STDCI code # To solve this issue we simply embedded the upstream sources code into the job code by using ‘{{#include}}’ in JJB rather then running it as a stand-alone script. # This technique is not usable for pipelines, so we need to come with a different solution and make the required adjustments to the source collection and polling code.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1515572840-15436-331--

1 0

[JIRA] (OVIRT-1759) Gerrit patches can reach CQ out-of-order
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1759?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1759: -------------------------------- Component/s: (was: oVirt CI) Gerrit/git Change Queue > Gerrit patches can reach CQ out-of-order > ---------------------------------------- > > Key: OVIRT-1759 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1759 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Change Queue, Gerrit/git > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: change-queue, gerrit > > Is seems that despite the fact that all the jobs involved were designed to preserve proper patch ordering, there can be cases where patches trigger Jenkins jobs in the wrong order, which in turn end up putting the patches in the wrong order into the CQ. This in turn, causes the CQ to fail accurately detecting the patches that cause issues. > Here is en example of such an occurance. The following patches were merged in the order specified below: > # https://gerrit.ovirt.org/c/83917 > # https://gerrit.ovirt.org/c/83918 > # https://gerrit.ovirt.org/c/83919 > # https://gerrit.ovirt.org/c/83920 > The standard-enqueue runs putting them in the CQ however, seem to have run in a different order: > # http://jenkins.ovirt.org/job/standard-enqueue/6712/ (83917) > # http://jenkins.ovirt.org/job/standard-enqueue/6713/ (83919) > # http://jenkins.ovirt.org/job/standard-enqueue/6714/ (83920) > # http://jenkins.ovirt.org/job/standard-enqueue/6715/ (83918) > This resulted in CQ 'add' command running in the wrong order: > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12200/ (add 83917) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12201/ (add 83919) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12202/ (add 83920) > # http://jenkins.ovirt.org/job/ovirt-master_change-queue/12203/ (add 83918) > We need to come up with a way to make the system properly preserver order. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1770) Build on fedora 26 fails, accessing console log extremely slow
by Barak Korren (oVirt JIRA) 10 Jan '18

10 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1770?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1770: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Build on fedora 26 fails, accessing console log extremely slow > -------------------------------------------------------------- > > Key: OVIRT-1770 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1770 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > Labels: jenkins > > I wait forever for this url: > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > here example: > $ time curl > http://jenkins.ovirt.org/job/ovirt-imageio_master_check-patch-fc26-x86_64/2… > > /dev/null > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 103k 0 103k 0 0 4814 0 --:--:-- 0:00:22 --:--:-- > 23562 > real 0m22.107s > user 0m0.005s > sys 0m0.009s > Can we fix to be less then a second? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0