February 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1167) repository copy from snapshots to tested-master stopped working
by Barak Korren (oVirt JIRA) 20 Feb '17

20 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1167?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1167: ----------------------------------- Assignee: Barak Korren (was: infra) > repository copy from snapshots to tested-master stopped working > --------------------------------------------------------------- > > Key: OVIRT-1167 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1167 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Greg Sheremeta > Assignee: Barak Korren > Priority: High > > The repository copy from snapshots to tested-master stopped working. > Thus, ovirt-js-dependencies is not available to developers. > /srv/resources/pub/ovirt-master-snapshot/rpm/fc24/SRPMS/ovirt-js-dependencies-0.0.3-2.fc24.src.rpm -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1167) repository copy from snapshots to tested-master stopped working
by Greg Sheremeta (oVirt JIRA) 20 Feb '17

20 Feb '17

Greg Sheremeta created OVIRT-1167: ------------------------------------- Summary: repository copy from snapshots to tested-master stopped working Key: OVIRT-1167 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1167 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Greg Sheremeta Assignee: infra Priority: High The repository copy from snapshots to tested-master stopped working. Thus, ovirt-js-dependencies is not available to developers. /srv/resources/pub/ovirt-master-snapshot/rpm/fc24/SRPMS/ovirt-js-dependencies-0.0.3-2.fc24.src.rpm -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1166) Please install Jenkins Pipeline-Milestone-Step-Plugin
by Nadav Goldin (oVirt JIRA) 20 Feb '17

20 Feb '17

Nadav Goldin created OVIRT-1166: ----------------------------------- Summary: Please install Jenkins Pipeline-Milestone-Step-Plugin Key: OVIRT-1166 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1166 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Nadav Goldin Assignee: infra The 'concurrency' parameter in the 'stage' step in the pipeline-plugin was deprecated, and is replaced by a combination of two new keywords 'lock' and 'milestone', however, the 'milestone' is included in a different plugin. This is required in order to allow gating, for now, in github projects. https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Milestone+Step+Plugin https://jenkins.io/blog/2016/10/16/stage-lock-milestone/ -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1166) Please install Jenkins Pipeline-Milestone-Step-Plugin
by Nadav Goldin (oVirt JIRA) 20 Feb '17

20 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1166?page=com.atlassian.jira.… ] Nadav Goldin updated OVIRT-1166: -------------------------------- Epic Link: OVIRT-403 > Please install Jenkins Pipeline-Milestone-Step-Plugin > ----------------------------------------------------- > > Key: OVIRT-1166 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1166 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Nadav Goldin > Assignee: infra > > The 'concurrency' parameter in the 'stage' step in the pipeline-plugin was deprecated, and is replaced by a combination of two new keywords 'lock' and 'milestone', however, the 'milestone' is included in a different plugin. > This is required in order to allow gating, for now, in github projects. > https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Milestone+Step+Plugin > https://jenkins.io/blog/2016/10/16/stage-lock-milestone/ -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1154) Make jenkins-whitelist use Gerrit groups
by Barak Korren (oVirt JIRA) 20 Feb '17

20 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1154: ------------------------------------- Looks like scanning for commiters in Git can be pretty fast with something like: {code} git log --pretty=format:%ae 'HEAD@{360 days ago}..' | sort -u {code} Here is timing this for engine master on my laptop: {code} $ time git log --pretty=format:%ae 'HEAD@{360 days ago}..' | sort -u | wc -l 118 real 0m0.143s user 0m0.124s sys 0m0.043s {code} So we can probably do this per-job. But it may cause issues if we want to switch to sparse or shallow clones. In the case we will need some kind of a nightly job to scan all branches of all projects to find committers and then store them somewhere. That 'somewhere' should probably just be a Gerrit group (Can it be? Need to check how easy is it to map emails to Gerrit users in practice). It may be more useful to somehow let maintainers (know contributors?) "confirm" a patch so that CI will check it, like we do for Lago. > Make jenkins-whitelist use Gerrit groups > ---------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1154) Make jenkins-whitelist use Gerrit groups
by Barak Korren (oVirt JIRA) 20 Feb '17

20 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1154 at 2/20/17 4:43 PM: -------------------------------------------------------------- We don't want to significantly slow down the CI because of this. A good guideline should be for the whole whitelist matching process to take: # At most 1 network fetch (right now it fetches once via cloning from Gerrit) # At most O\(n) time to search the match, where 'n' is the *number of contributors* as opposed to *number of patches* AFAIK we don't keep lists of contributors anywhere ATM, so we'll probably need to scan patches to see who contributed. We may not be able to practically do this fast enough. We will need to check if Git or Gerrit can do this efficiently for us ahead of time. We also need some proper definition of who is considered a contributor. I don't think that someone with a merged patch ever is a good heuristic, should probably be something like N patches merged in the last M months. was (Author: bkorren(a)redhat.com) We don't want to significantly slow down the CI because of this, a good guideline should be for the whole whitelist matching process to take: # At most 1 network fetch (right not if fetches once via cloning from Gerrit) # At most O\(n) time to search the match, where 'n' is the *number of contributors* as opposed to *number of patches* AFAIK we don't keep lists of contributors anywhere ATM, so we'll probably need to scan patches to see who contributed. We may not be able to practically do this fast enough. We will need to check if Git or Gerrit can do this efficiently for us ahead of time. We also need some proper definition of who is considered a contributor. I don't think that someone with a merged patch ever is a good heuristic, should probably be something like N patches merged in the last M months. > Make jenkins-whitelist use Gerrit groups > ---------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1165) Please add 'gerrit reviewer plugin'
by eyal edri [Administrator] (oVirt JIRA) 20 Feb '17

20 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1165?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1165: ------------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > Please add 'gerrit reviewer plugin' > ----------------------------------- > > Key: OVIRT-1165 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1165 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: rgolan > Assignee: Evgheni Dereveanchin > > Hi infra > It would be very useful for projects to use the 'reviewers' gerrit plugin. > It's a prefix configuration base pluging to add users or gerrit groups. > Every project maintainers would have to then decide on the configuration. > Example [1] of a project's `reviewers.config` > [filter "*"] > reviewer = john.doe(a)example.com > [filter "branch:main file:^lib/.*"] > reviewer = jane.doe(a)example.com > [filter "branch:stable-2.10"] > reviewer = QAGroup > [filter "file:^build/modules/.*"] > reviewer = john.doe(a)example.com > [filter "file:^build/.*"] > reviewer = jane.doe(a)example.com > Thanks, > Roy > [1] https://gerrit.googlesource.com/plugins/reviewers/+/master/src/main/resourc… -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[JIRA] (OVIRT-1165) Please add 'gerrit reviewer plugin'
by rgolan (oVirt JIRA) 20 Feb '17

20 Feb '17

rgolan created OVIRT-1165: ----------------------------- Summary: Please add 'gerrit reviewer plugin' Key: OVIRT-1165 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1165 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: rgolan Assignee: infra Hi infra It would be very useful for projects to use the 'reviewers' gerrit plugin. It's a prefix configuration base pluging to add users or gerrit groups. Every project maintainers would have to then decide on the configuration. Example [1] of a project's `reviewers.config` [filter "*"] reviewer = john.doe(a)example.com [filter "branch:main file:^lib/.*"] reviewer = jane.doe(a)example.com [filter "branch:stable-2.10"] reviewer = QAGroup [filter "file:^build/modules/.*"] reviewer = john.doe(a)example.com [filter "file:^build/.*"] reviewer = jane.doe(a)example.com Thanks, Roy [1] https://gerrit.googlesource.com/plugins/reviewers/+/master/src/main/resourc… -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0

[ OST Failure Report ] [ ovirt 4.0 ] [ 17.02.17 ] [ add hosts ]
by Dusan Fodor 20 Feb '17

20 Feb '17

Hello, python cpopen missing error occured while deploying host: 2017-02-16 21:44:28 ERROR otopi.plugins.otopi.packagers.yumpackager yumpackager.error:85 Yum [u'python-ioprocess-0.16.1-1.el7.noarch requires python-cpopen', u'vdsm-4.18.21-1.el7.centos.x86_64 requires python-cpopen >= 1.4', u'vdsm-python-4.18.21-1.el7.centos.noarch requires python-cpopen >= 1.4'] Could you please assist? Thanks Link to build: http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_4.0_system-t… Link to host-deploy log: http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_4.0_system-t…

4 4

[JIRA] (OVIRT-1154) Make jenkins-whitelist use Gerrit groups
by Michal Skrivanek (oVirt JIRA) 20 Feb '17

20 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1154: ----------------------------------------- - I suppose the list of contributors should be cached and refreshed e.g. once a day - single merged patch should be good enough, maybe not the whole history indeed, perhaps last 2 years would be ok > Make jenkins-whitelist use Gerrit groups > ---------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.769.1#100032)

1 0