June 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1248) Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1248?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1248: -------------------------------- Component/s: (was: oVirt CI) CI client projects > Make SDK Standard-CI jobs show "friendly" output when blocked by whitelist > -------------------------------------------------------------------------- > > Key: OVIRT-1248 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1248 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > > Most Standard-CI jobs, when blocked by whitelist yield a "NOTRUN" result and a message explaining what happened. > The SDK jobs set CI -1 instead. > It seems that it is because they are missing the Groovy post-build script that sets up the specialized whitelist output. > This is probably because the YAML of the SDK jobs is different from all other jobs (see OVIRT-1247) , so they got overlooked when some if the whitelist changes were introduced. > We need to fix this unless OVIRT-1247 gets fixed sooner. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1252: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) This issue is not relevant for STDCI V2 as all post-merge actions happen within the same job. So closing Wontfix > post-merge build-artifacts jobs can run out of order > ---------------------------------------------------- > > Key: OVIRT-1252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. > The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. > To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-2231) QEMU can't access "/home/jenkins/*" on FC28 slaves.

by Gal Ben Haim (oVirt JIRA)

Gal Ben Haim created OVIRT-2231: ----------------------------------- Summary: QEMU can't access "/home/jenkins/*" on FC28 slaves. Key: OVIRT-2231 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2231 Project: oVirt - virtualization made easy Issue Type: Bug Components: Lago Reporter: Gal Ben Haim Assignee: infra Priority: Highest Lago creates VM images under "/home/jenkins", QEMU process fails to access those images because of missing permissions. The solution is to set the "execute/search" bit on "/home/jenkins". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1252: -------------------------------- Epic Link: (was: OVIRT-400) > post-merge build-artifacts jobs can run out of order > ---------------------------------------------------- > > Key: OVIRT-1252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. > The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. > To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1252: -------------------------------- Epic Link: (was: OVIRT-400) > post-merge build-artifacts jobs can run out of order > ---------------------------------------------------- > > Key: OVIRT-1252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. > The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. > To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1276) generate a link to OST automation job

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1276: -------------------------------- Resolution: Duplicate Status: Done (was: To Do) > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST Manual job > Reporter: Roy Golan > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1276) generate a link to OST automation job

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1276: -------------------------------- Component/s: OST Manual job > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST Manual job > Reporter: Roy Golan > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1276) generate a link to OST automation job

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1276: -------------------------------- Epic Link: (was: OVIRT-400) > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Roy Golan > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-1276) generate a link to OST automation job

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1276: -------------------------------- Epic Link: (was: OVIRT-400) > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Roy Golan > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 6 months

1
0
0 / 0

[JIRA] (OVIRT-2221) Reposync builder will not work with DNF

by Gal Ben Haim (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2221?page=com.atlassian.jir... ] Gal Ben Haim updated OVIRT-2221: -------------------------------- Summary: Reposync builder will not work with DNF (was: Reposync builder will no work with DNF ) > Reposync builder will not work with DNF > ---------------------------------------- > > Key: OVIRT-2221 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2221 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > Part of the reposync builder tool is a Yum plugin which auto-generates the reposync-config with "includepkgs" field. > DNF doesn't support Yum plugins, so we will have to rewrite the plugin for DNF, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018