May 2017 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-1408: ------------------------------------- If you just remove 'automation', you'll just get broken jobs. You need to remove the jobs themselves by removing the project YAML from the 'jenkins' repo. > Please remove github/ovirt-web-ui from standard CI > -------------------------------------------------- > > Key: OVIRT-1408 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please remove github/ovirt-web-ui from standard CI since Travis is used instead. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI

by Michal Skrivanek (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jir... ] Michal Skrivanek commented on OVIRT-1408: ----------------------------------------- [~mlibra(a)redhat.com], I wonder what is being requested from infra? Why you can't simply remove the automation/ directory in the project when it's not needed? Does it break anything? > Please remove github/ovirt-web-ui from standard CI > -------------------------------------------------- > > Key: OVIRT-1408 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please remove github/ovirt-web-ui from standard CI since Travis is used instead. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1409) Build oVirt 4.1.3 tc1

by sbonazzo (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1409?page=com.atlassian.jir... ] sbonazzo updated OVIRT-1409: ---------------------------- Assignee: sbonazzo (was: infra) Status: In Progress (was: To Do) > Build oVirt 4.1.3 tc1 > --------------------- > > Key: OVIRT-1409 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1409 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: oVirt Release Mgmt > Reporter: sbonazzo > Assignee: sbonazzo > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1409) Build oVirt 4.1.3 tc1

by sbonazzo (oVirt JIRA)

sbonazzo created OVIRT-1409: ------------------------------- Summary: Build oVirt 4.1.3 tc1 Key: OVIRT-1409 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1409 Project: oVirt - virtualization made easy Issue Type: Task Components: oVirt Release Mgmt Reporter: sbonazzo Assignee: infra Priority: Highest -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1409) Build oVirt 4.1.3 tc1

by sbonazzo (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1409?page=com.atlassian.jir... ] sbonazzo updated OVIRT-1409: ---------------------------- Epic Link: OVIRT-411 > Build oVirt 4.1.3 tc1 > --------------------- > > Key: OVIRT-1409 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1409 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: oVirt Release Mgmt > Reporter: sbonazzo > Assignee: infra > Priority: Highest > -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1239) tracking ticket for supporting multiple organization in GH CR builder plugin

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1239?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1239: --------------------------------------------- Epic Link: OVIRT-403 > tracking ticket for supporting multiple organization in GH CR builder plugin > ---------------------------------------------------------------------------- > > Key: OVIRT-1239 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1239 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Lowest > > In current implementation credentials can be specified only per server so it's not possible to use different credentials for ovirt and lago projects using same jenkins instance as we do. > During meeting with [~eedri] we decided to evaluate two possible options: > 1) Webhooks to trigger build. From first glance it looks good but not sure if it's solve the problem with credentials. It should be implemented anyway and it's tracked under OVIRT-1142 > 2) Open RFE under GH PR Builder plugin to support this out of the box. > This ticket is opened to track progress on second option. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1239) tracking ticket for supporting multiple organization in GH CR builder plugin

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1239?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1239: --------------------------------------------- Epic Link: OVIRT-403 > tracking ticket for supporting multiple organization in GH CR builder plugin > ---------------------------------------------------------------------------- > > Key: OVIRT-1239 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1239 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Lowest > > In current implementation credentials can be specified only per server so it's not possible to use different credentials for ovirt and lago projects using same jenkins instance as we do. > During meeting with [~eedri] we decided to evaluate two possible options: > 1) Webhooks to trigger build. From first glance it looks good but not sure if it's solve the problem with credentials. It should be implemented anyway and it's tracked under OVIRT-1142 > 2) Open RFE under GH PR Builder plugin to support this out of the box. > This ticket is opened to track progress on second option. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1271) GH plugin tries to consume gerrit's projects

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1271?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1271: --------------------------------------------- Epic Link: OVIRT-403 > GH plugin tries to consume gerrit's projects > -------------------------------------------- > > Key: OVIRT-1271 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1271 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > Jenkins logs are flooded with: > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins-whitelist.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL git://gerrit.ovirt.org/vdsm.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git > While the messages itself are harmless they floods the logs and consume jenkins master's resources. > See https://issues.jenkins-ci.org/browse/JENKINS-24422 for more details. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1271) GH plugin tries to consume gerrit's projects

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1271?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1271: --------------------------------------------- Epic Link: OVIRT-403 > GH plugin tries to consume gerrit's projects > -------------------------------------------- > > Key: OVIRT-1271 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1271 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > Jenkins logs are flooded with: > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins-whitelist.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL git://gerrit.ovirt.org/vdsm.git > Mar 23, 2017 10:40:05 AM com.cloudbees.jenkins.GitHubRepositoryName create > WARNING: Could not match URL http://gerrit.ovirt.org/jenkins.git > While the messages itself are harmless they floods the logs and consume jenkins master's resources. > See https://issues.jenkins-ci.org/browse/JENKINS-24422 for more details. -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1318) configure backup of status.ovirt.org

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1318?page=com.atlassian.jir... ] eyal edri [Administrator] updated OVIRT-1318: --------------------------------------------- Epic Link: OVIRT-403 > configure backup of status.ovirt.org > ------------------------------------ > > Key: OVIRT-1318 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1318 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > status.ovirt.org was set up - need to investigate if it needs to be backed up or we can produce documentation to set up a new stats page in case something happens to the existing OpenShift gear. > We can use OpenShift's built in backup/restore functionality: > https://developers.openshift.com/managing-your-applications/backing-up-ap... -- This message was sent by Atlassian JIRA (v1000.1010.0#100044)

7 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra May 2017