March 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1254) add to infra docs on supporting building containers in std ci
by eyal edri [Administrator] (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1254?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1254: ------------------------------------------------ Assignee: Daniel Belenky (was: infra) > add to infra docs on supporting building containers in std ci > ------------------------------------------------------------- > > Key: OVIRT-1254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1254 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > Priority: High > > We now support building containers in standard CI. > we need to document how a developer will use it and to give example the ovirt-container-engine once it works. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1254) add to infra docs on supporting building containers in std ci
by eyal edri [Administrator] (oVirt JIRA) 13 Mar '17

13 Mar '17

eyal edri [Administrator] created OVIRT-1254: ------------------------------------------------ Summary: add to infra docs on supporting building containers in std ci Key: OVIRT-1254 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1254 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Priority: High We now support building containers in standard CI. we need to document how a developer will use it and to give example the ovirt-container-engine once it works. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1254) add to infra docs on supporting building containers in std ci
by eyal edri [Administrator] (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1254?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1254: --------------------------------------------- Epic Link: OVIRT-400 > add to infra docs on supporting building containers in std ci > ------------------------------------------------------------- > > Key: OVIRT-1254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1254 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > We now support building containers in standard CI. > we need to document how a developer will use it and to give example the ovirt-container-engine once it works. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1073) Gradually remove jobs from master publisher
by eyal edri [Administrator] (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1073?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1073: ------------------------------------------------ Assignee: eyal edri [Administrator] (was: infra) > Gradually remove jobs from master publisher > ------------------------------------------- > > Key: OVIRT-1073 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1073 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: eyal edri [Administrator] > > We saw how destructive using the current publishers can be during 4.1 cycle, > Problems we encountered: > 1. It hides missing RPMs from experimental flows > 2. It hides projects that needs to branch or using previous version released > 3. It creates confusion of which RPMs are really tested in OST and give different results than experimental instead of having a single source of RPMs for oVirt. > We should aim to drop it for 4.2 and use only experimental deployment. > However, since we have errors on deploy to experimental flow, we can't progress with this until they will be solved. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Barak Korren (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1250: ------------------------------------- Can we generalize it to the point where we will have just one pipeline job that will do all the triggering for all projects (E.g based on the existence of jobs for those projects)? > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5795 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Mar '17

13 Mar '17

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

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5793 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 13 Mar '17

13 Mar '17

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

1 1

[JIRA] (OVIRT-1253) document PHX OpenVPN
by Evgheni Dereveanchin (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1253?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1253: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > document PHX OpenVPN > -------------------- > > Key: OVIRT-1253 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1253 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > document the service and how to add users -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1253) document PHX OpenVPN
by Evgheni Dereveanchin (oVirt JIRA) 13 Mar '17

13 Mar '17

Evgheni Dereveanchin created OVIRT-1253: ------------------------------------------- Summary: document PHX OpenVPN Key: OVIRT-1253 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1253 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra document the service and how to add users -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Pavel Zhukov (oVirt JIRA) 13 Mar '17

13 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] Pavel Zhukov commented on OVIRT-1250: ------------------------------------- [~bkorren(a)redhat.com] [~eedri] Right. But it's not purpose of this ticket. The problem is this "you're not in whitelist" message is sent 4 (or more) times. It's pointless. The only solution I can see now is pipeline (again). We have to check whitelist if user is not whitelisted then give them one single message otherwise trigger other jobs (per branch/OS). > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0