April 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1317) gather analytics data from oVirt website
by Evgheni Dereveanchin (oVirt JIRA) 12 Apr '17

12 Apr '17

Evgheni Dereveanchin created OVIRT-1317: ------------------------------------------- Summary: gather analytics data from oVirt website Key: OVIRT-1317 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1317 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Piwik was set up to replace the old stats server. Now related JS needs to be added to the website so that analytics data is sent to Piwik -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

[JIRA] (OVIRT-1317) gather analytics data from oVirt website
by Evgheni Dereveanchin (oVirt JIRA) 12 Apr '17

12 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1317?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1317: ---------------------------------------- Epic Link: OVIRT-840 > gather analytics data from oVirt website > ---------------------------------------- > > Key: OVIRT-1317 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1317 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > Piwik was set up to replace the old stats server. Now related JS needs to be added to the website so that analytics data is sent to Piwik -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #6313 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 Apr '17

12 Apr '17

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

1 19

[JIRA] (OVIRT-1316) Allow parallel invocation of the manual OST job
by Barak Korren (oVirt JIRA) 12 Apr '17

12 Apr '17

Barak Korren created OVIRT-1316: ----------------------------------- Summary: Allow parallel invocation of the manual OST job Key: OVIRT-1316 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1316 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Currently parallel executions are not allowed. This is making developers have to wait in line to run it. We can probably afford to have 3-4 parallel runs. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

[JIRA] (OVIRT-1316) Allow parallel invocation of the manual OST job
by Barak Korren (oVirt JIRA) 12 Apr '17

12 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1316?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1316: -------------------------------- Epic Link: OVIRT-400 > Allow parallel invocation of the manual OST job > ----------------------------------------------- > > Key: OVIRT-1316 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1316 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Currently parallel executions are not allowed. This is making developers have to wait in line to run it. > We can probably afford to have 3-4 parallel runs. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

[JIRA] (OVIRT-1315) post-merge build-artifacts jobs for the same commit have a race condition between different platforms
by Barak Korren (oVirt JIRA) 12 Apr '17

12 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1315?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1315: ------------------------------------- [~sbonazzo(a)redhat.com] That will probably require rewriting STC-CI jobs to be 'Jenkins Pipeline' jobs. This may be the long term solution but its is a considerable rewrite, so we are not eager to go down that road just yet. One downside of this is that the project-specific YAML files will probably have to change, unless we also get to implementing OVIRT-1013. I'm hoping we can find some trick to make "deploy to experimental" figure out there are still some more build jobs for the same commit running and wait for them. We will probably need to rewrite it too, but I'm thinking this may be a simpler and less visible rewrite then for 'build artifacts'. I may be wrong about that though. > post-merge build-artifacts jobs for the same commit have a race condition between different platforms > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-1315 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1315 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > When a change is merged the build artifacts jobs for all platforms are invoked in parallel by the Gerrit trigger. These jobs in turn invoej the 'deploy-to-experimental' job to move the artifacts into the 'experimental' repos for OST testing. > Various issues arise because of this: > # A Fedora build can trigger an OST run befire the equivalent EL7 build finishes. This wastes resources on needless OST runs. > # A PPC64 build can place 'noarch' artifacts in experimental before the equivalent x86_64 builds are ready. This can cause OST failures. > Because of the PPC64 issue, we have actually disabled publishing into experimental from the PPC64 jobs. Since we now want to move to fully automated production publishing via the experimental flow, we need to fix this. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

[JIRA] (OVIRT-1315) post-merge build-artifacts jobs for the same commit have a race condition between different platforms
by sbonazzo (oVirt JIRA) 12 Apr '17

12 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1315?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-1315: --------------------------------- [~bkorren(a)redhat.com] can we change stdci to have a single build job that trigger all the different distro/arch builds, wait until they finishes and then finish with success if all succeeded and trigger the deploy job? This is valid for all projects, not only vdsm. It doesn't make sense to have different versions/builds available for different arches/distro. > post-merge build-artifacts jobs for the same commit have a race condition between different platforms > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-1315 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1315 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > When a change is merged the build artifacts jobs for all platforms are invoked in parallel by the Gerrit trigger. These jobs in turn invoej the 'deploy-to-experimental' job to move the artifacts into the 'experimental' repos for OST testing. > Various issues arise because of this: > # A Fedora build can trigger an OST run befire the equivalent EL7 build finishes. This wastes resources on needless OST runs. > # A PPC64 build can place 'noarch' artifacts in experimental before the equivalent x86_64 builds are ready. This can cause OST failures. > Because of the PPC64 issue, we have actually disabled publishing into experimental from the PPC64 jobs. Since we now want to move to fully automated production publishing via the experimental flow, we need to fix this. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

[JIRA] (OVIRT-1315) post-merge build-artifacts jobs for the same commit have a race condition between different platforms
by Barak Korren (oVirt JIRA) 12 Apr '17

12 Apr '17

Barak Korren created OVIRT-1315: ----------------------------------- Summary: post-merge build-artifacts jobs for the same commit have a race condition between different platforms Key: OVIRT-1315 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1315 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: High When a change is merged the build artifacts jobs for all platforms are invoked in parallel by the Gerrit trigger. These jobs in turn invoej the 'deploy-to-experimental' job to move the artifacts into the 'experimental' repos for OST testing. Various issues arise because of this: # A Fedora build can trigger an OST run befire the equivalent EL7 build finishes. This wastes resources on needless OST runs. # A PPC64 build can place 'noarch' artifacts in experimental before the equivalent x86_64 builds are ready. This can cause OST failures. Because of the PPC64 issue, we have actually disabled publishing into experimental from the PPC64 jobs. Since we now want to move to fully automated production publishing via the experimental flow, we need to fix this. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

[JIRA] (OVIRT-1315) post-merge build-artifacts jobs for the same commit have a race condition between different platforms
by Barak Korren (oVirt JIRA) 12 Apr '17

12 Apr '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1315?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1315: -------------------------------- Epic Link: OVIRT-400 > post-merge build-artifacts jobs for the same commit have a race condition between different platforms > ----------------------------------------------------------------------------------------------------- > > Key: OVIRT-1315 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1315 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > When a change is merged the build artifacts jobs for all platforms are invoked in parallel by the Gerrit trigger. These jobs in turn invoej the 'deploy-to-experimental' job to move the artifacts into the 'experimental' repos for OST testing. > Various issues arise because of this: > # A Fedora build can trigger an OST run befire the equivalent EL7 build finishes. This wastes resources on needless OST runs. > # A PPC64 build can place 'noarch' artifacts in experimental before the equivalent x86_64 builds are ready. This can cause OST failures. > Because of the PPC64 issue, we have actually disabled publishing into experimental from the PPC64 jobs. Since we now want to move to fully automated production publishing via the experimental flow, we need to fix this. -- This message was sent by Atlassian JIRA (v1000.892.1#100040)

1 0

oVirt infra daily report - unstable production jobs - 288
by jenkins＠jenkins.phx.ovirt.org 12 Apr '17

12 Apr '17

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/288//artifact/exported-a… Cheers, Jenkins

1 1