- Infra - oVirt List Archives

[JIRA] (OVIRT-970) Add support for GitHub projects in standard CI
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-970?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-970: ----------------------------------------------- Assignee: Pavel Zhukov (was: infra) This can get started regardless of the projects who wish to join, we need to have the support in templates,triggers,builders first, so when we want to add new projects, the templates will be ready. Most of the work should start at: (on jenkins repo) jobs/confs/yaml/triggers/github.yml jobs/confs/yaml/templates/standard-stage.yml > Add support for GitHub projects in standard CI > ---------------------------------------------- > > Key: OVIRT-970 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-970 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: Pavel Zhukov > > Needed for https://ovirt-jira.atlassian.net/browse/OVIRT-874 > We have GitHub templates already in YAML, but they are very specific for Lago and not sure they support all the stages of standard CI. > We need to update the templates so it'll be easy to add new project from GitHub if we want to. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-970) Add support for GitHub projects in standard CI
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-970?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-970: -------------------------------------------- Epic Link: OVIRT-400 > Add support for GitHub projects in standard CI > ---------------------------------------------- > > Key: OVIRT-970 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-970 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > > Needed for https://ovirt-jira.atlassian.net/browse/OVIRT-874 > We have GitHub templates already in YAML, but they are very specific for Lago and not sure they support all the stages of standard CI. > We need to update the templates so it'll be easy to add new project from GitHub if we want to. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-970) Add support for GitHub projects in standard CI
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

eyal edri [Administrator] created OVIRT-970: ----------------------------------------------- Summary: Add support for GitHub projects in standard CI Key: OVIRT-970 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-970 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: eyal edri [Administrator] Assignee: infra Needed for https://ovirt-jira.atlassian.net/browse/OVIRT-874 We have GitHub templates already in YAML, but they are very specific for Lago and not sure they support all the stages of standard CI. We need to update the templates so it'll be easy to add new project from GitHub if we want to. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-969) Install new gerrit plugin: Gerrit webhooks plugin
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-969?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-969: -------------------------------------------- Epic Link: OVIRT-403 > Install new gerrit plugin: Gerrit webhooks plugin > ------------------------------------------------- > > Key: OVIRT-969 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-969 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > Info at https://github.com/GetBadges/gerrit-webhooks. > cc [~sbendavi(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-969) Install new gerrit plugin: Gerrit webhooks plugin
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

eyal edri [Administrator] created OVIRT-969: ----------------------------------------------- Summary: Install new gerrit plugin: Gerrit webhooks plugin Key: OVIRT-969 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-969 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Info at https://github.com/GetBadges/gerrit-webhooks. cc [~sbendavi(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4369 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 22 Dec '16

22 Dec '16

------=_Part_122_182305068.1482407495345 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4369/, Build Number: 4369, Build Status: FAILURE ------=_Part_122_182305068.1482407495345--

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4365 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 22 Dec '16

22 Dec '16

------=_Part_106_599148934.1482399766403 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4365/, Build Number: 4365, Build Status: FAILURE ------=_Part_106_599148934.1482399766403--

1 2

[JIRA] (OVIRT-296) [jenkins] take offline faulty bad slaves
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-296?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-296: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > [jenkins] take offline faulty bad slaves > ---------------------------------------- > > Key: OVIRT-296 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-296 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > Labels: jenkins, monitoring, > > it seems that quite often we hit an issue with a specific slave on phx, due to various reasons (out of space/git/network/etc..). > which leads to multiple jobs trying to run on it and failing. > we need an automated way of finding this. > proposal: > add post groovy build to jobs that will take a slave offline if it's misbehaves using: > manager.build.getBuiltOn().toComputer.setTemporarilyOffline(true) > the trick is to find such a slave and to be able to know if it failed consistently in the past X hours to justify it's disable. > we need some sort of counter or service to track slaves and thier error state and according to it take offline a specific slave. > for example: > if a slave was failing x jobs in Y time and runtime was < Z min , it might indicate such a problem. > (e.g 10 jobs were failing on the same slave in a timeframe of 5 min and job runtime was less than a 1 min.. ) > the post script should email infra(a)ovirt.org that it disabled a slave and we should look into it. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-226: -------------------------------------------- Resolution: Won't Do (was: Won't Fix) Status: Done (was: To Do) Already tracked by QE, see more info on the Bugzilla bug. > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > ---------------------------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: sbonazzo > Assignee: infra > Priority: Lowest > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0

[JIRA] (OVIRT-20) Document oVirt infra SLA
by eyal edri [Administrator] (oVirt JIRA) 22 Dec '16

22 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-20?page=com.atlassian.jira.pl… ] eyal edri [Administrator] reassigned OVIRT-20: ---------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Document oVirt infra SLA > ------------------------- > > Key: OVIRT-20 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-20 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: quaid > Assignee: Evgheni Dereveanchin > Priority: Highest > > We need to document how we make changes: > * What services need notices out to the world? > * What are the timeframes for notices? > \\- 1 hour for critical > \\- 12 to 24 hours for non-critical > * Who needs to be notified for what? > \\- e.g. leave announce out of administrivia > \\- arch, users, and infra are the defaults so far > \\- perhaps create an infra-announce list that just includes the others? > * When do we not make changes? > \\- change freeze around releases > \\- other change freeze reasons > * What is the process to make a change during a freeze? > \\- When is the freeze slushy? > \\- When is the freeze solid and should not be broken because of the potential risk at that moment? (We need something to weigh risk against risk.) -- This message was sent by Atlassian JIRA (v1000.621.5#100023)

1 0