January 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1689) Improve error messages in STDCI environment variable handling

by Barak Korren (oVirt JIRA)

This is a multi-part message in MIME format... ------------=_1515574161-11214-315 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1689?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1689: -------------------------------- Component/s: (was: oVirt CI) mock_runner > Improve error messages in STDCI environment variable handling > ------------------------------------------------------------- > > Key: OVIRT-1689 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1689 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Daniel Belenky > Assignee: infra > > * All references to things like 'xdg-home' need to be replaced with specifications of actual paths, as users are not expected to know what XDG is. > * Accurate indication of what is missing from which file and what can be done to fix it need to be given in all error messages. > * When variable/key names are given in error messages, they need to be quoted for clarity. > * Edge cases like for example an existing but empty secrets file and a missing 'secrets_data' key need to be handled better, with clear error messages > * Error message when a requested env var is missing needs to be improved to tell the user what to do. Current message can be very confusing when trying to use 'mock_runner.sh' for the 'jenkins' repo for example. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1515574161-11214-315 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1689?page=com.atlassian.jir... ]</pre> <h3>Barak Korren updated OVIRT-1689:</h3> <pre> Component/s: (was: oVirt CI) mock_runner</pre> <blockquote><h3>Improve error messages in STDCI environment variable handling</h3> <pre> Key: OVIRT-1689 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1689 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Daniel Belenky Assignee: infra</pre> <ul><li><p>All references to things like ‘xdg-home’ need to be replaced with specifications of actual paths, as users are not expected to know what XDG is.</p></li> <li><p>Accurate indication of what is missing from which file and what can be done to fix it need to be given in all error messages.</p></li> <li><p>When variable/key names are given in error messages, they need to be quoted for clarity.</p></li> <li><p>Edge cases like for example an existing but empty secrets file and a missing ‘secrets_data’ key need to be handled better, with clear error messages</p></li> <li><p>Error message when a requested env var is missing needs to be improved to tell the user what to do. Current message can be very confusing when trying to use ‘mock_runner.sh’ for the ‘jenkins’ repo for example.</p></li></ul></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-2BJ33BS..." 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> ------------=_1515574161-11214-315--

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1690) Add CI for groovy/pipeline code in 'jenkins' repo

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1690?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1690: -------------------------------- Component/s: (was: oVirt CI) CI client projects > Add CI for groovy/pipeline code in 'jenkins' repo > ------------------------------------------------- > > Key: OVIRT-1690 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1690 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > Labels: groovy, jenkins > > We don't have any CI for Groovy code currently. > At the very least we need to check that the code compiles, this is a bit harder then it sounds because in order to test compilation for piepline code we need to mock out things like the '{{NonCPS}}' decorator which is not supported by the standard Groovy compiler. > Ideally we can also ass support for a full test suit. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1717: -------------------------------- Component/s: (was: oVirt CI) Change Queue > When a component build passes OST, tag its git hash > --------------------------------------------------- > > Key: OVIRT-1717 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: danken > Assignee: infra > Labels: change-queue, standard-ci > > Tagging the source git would make it easier for me to tell if a specific git commit is already tested by OST and available for QA. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jir... ] 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)

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jir... ] 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)

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jir... ] 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)

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jir... ] 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)

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1739?page=com.atlassian.jir... ] 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)

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1743) ci please build and send to OST

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jir... ] 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)

6 years, 10 months

1
0
0 / 0

[JIRA] (OVIRT-1743) ci please build and send to OST

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1743?page=com.atlassian.jir... ] 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)

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra January 2018