- Infra - oVirt List Archives

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#31). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 68 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/31 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 31 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

[JIRA] (OVIRT-2230) Checkout using prow as a GitHub triggering mechanism
by Barak Korren (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2230?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2230: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) that was an attempt ot integrate Prow with stdci - but Kubevirt decided to go 100% prow > Checkout using prow as a GitHub triggering mechanism > ---------------------------------------------------- > > Key: OVIRT-2230 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2230 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master > Reporter: Barak Korren > Assignee: infra > > [Prow|https://github.com/kubernetes/test-infra/tree/master/prow] is the service that Kubernetes are using to trigger their CI on GitHub events. > We should inspect it and see if it would be useful for us to adopt it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2342) Create a repo called ovirt-engine-config
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2342?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2342: ---------------------------------- What this needed in the end? I don’t see a repo created. > Create a repo called ovirt-engine-config > ----------------------------------------- > > Key: OVIRT-2342 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2342 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: GitHub > Reporter: Tareq Alayan > Assignee: infra > > the repo will contain the ansible role representing the ovirt-engine-config utility -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2443) Make sure that big containers KubVirt CI uses are cached on hosts
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2443?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2443: ---------------------------------- [~dbelenky(a)redhat.com] [~gbenhaim(a)redhat.com] [~bkorren(a)redhat.com] any update on this? > Make sure that big containers KubVirt CI uses are cached on hosts > ----------------------------------------------------------------- > > Key: OVIRT-2443 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2443 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > > Make sure that big containers KubVirt CI uses are cached on hosts -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1984) Create "out-of-band" slave cleanup and setup jobs
by Barak Korren (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1984?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1984: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > Create "out-of-band" slave cleanup and setup jobs > ------------------------------------------------- > > Key: OVIRT-1984 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1984 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Right now, we run slave cleaup and setup steps as part or every single job we run. This has several shortcomings: > # It takes a long time from the point a user submitted a patch to the point his actual test or build code runs > # If slave setup or cleanup steps fail - they fail the whole job for the user > # If slave setup or cleanup steps fail - they can keep failing for many jobs until the CI team intervenes manually > # There is a "chicken and an egg" issue where some parts of the CI code have to run before the slave was properly cleaned up and configured. This makes if harder to add new slaves for the system. > Here is a suggested scheme to fix all this: > # Label all slaves that should be cleaned up automatically as 'cleanable'. This is mostly to prevent the jobs described here from operating on the master node. > # Have a "cleanup scheduler" job that finds all slaves labelled as "cleanable" but not as "dirty" or "clean", labels them as "dirty" and runs a cleanup job on them. > # Have a "cleanup" job that is triggered on particular slaves by the "cleanup scheduler" job, runs cleaup and setup steps on them and then labels them as "clean" and removes the "dirty" label. > # Have all other CI jobs only use slaves with the "clean" label. > Notes: > # The "dirty" label is there to make the "cleanup scheduler" job not trigger twice on the same slave before the"cleanup" job started cleaning it up. > # Since all slaves used by the real jobs will always be clean - there will no longer be a need to run cleanup steps in the real jobs, thus saving time. > # If cleanup steps fail - the cleanup job will fail and the slave will not be marked as "clean" so real jobs will never try to use it. > # To solve the "chicken and egg" issue, the cleanup job probably must be a FreeStyle jobs and all the cleanup and setup code must be embedded into it by JJB. This will probably require a newer version of JJB then what we have so setting OVIRT-1983 as a blocker. > # There is an issue of how to make CI for this - if cleanup and setup steps are removed from the normal STDCI jobs, they they will not be checked by the "check-patch" job of the "jenkins repo". Here is a suggested scheme to solve this: > ## Have a way to "loan" slaves from the production jenkins to other Jenkins instances - this could be done by having a job that starts up the Jenkins JNLP client and tells it to connect to another Jenkins master. > ## As part of the "check-patch" job for the 'jenkins' repo - start a Jenkins master in a container - attach some production slaves to it and have it run cleanup and setup steps on them -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2178) "Borrow" slaves from CentOS CI
by Barak Korren (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2178?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2178: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > "Borrow" slaves from CentOS CI > ------------------------------ > > Key: OVIRT-2178 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2178 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: Barak Korren > Assignee: infra > > [CentOS CI|https://wiki.centos.org/QaWiki/CI] is a generic shared platform for building CI service for Open Source projects. > Amount other things, CentOS CI makes physical and virtual hosts available for running CI processes via the [Duffy|http://wiki.centos.org/QaWiki/CI/Duffy] system. > We should make oVirt CI able to consume resources from CentOs CI to augment and someday replace the hardware resources available to oVirt CI. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#30). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 67 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/30 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 30 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

[JIRA] (OVIRT-2230) Checkout using prow as a GitHub triggering mechanism
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2230?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2230: ---------------------------------- Since KubeVirt are doing it already, is there anything left to do on this ticket? I don’t expect oVirt to move to it. > Checkout using prow as a GitHub triggering mechanism > ---------------------------------------------------- > > Key: OVIRT-2230 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2230 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master > Reporter: Barak Korren > Assignee: infra > > [Prow|https://github.com/kubernetes/test-infra/tree/master/prow] is the service that Kubernetes are using to trigger their CI on GitHub events. > We should inspect it and see if it would be useful for us to adopt it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Barak Korren (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-886: ------------------------------------ Reopening ticket - issue still relevant. > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2178) "Borrow" slaves from CentOS CI
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2178?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2178: ---------------------------------- I think we agreed this won’t be a viable solution, so I think we can close this ticket. > "Borrow" slaves from CentOS CI > ------------------------------ > > Key: OVIRT-2178 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2178 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: Barak Korren > Assignee: infra > > [CentOS CI|https://wiki.centos.org/QaWiki/CI] is a generic shared platform for building CI service for Open Source projects. > Amount other things, CentOS CI makes physical and virtual hosts available for running CI processes via the [Duffy|http://wiki.centos.org/QaWiki/CI/Duffy] system. > We should make oVirt CI able to consume resources from CentOs CI to augment and someday replace the hardware resources available to oVirt CI. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by Dafna Ron (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-1919: ---------------------------------- sure. I am not sure how many projects are still using github as I did not see commits from there for a while. > missing documentation on ci re-merge please in github > ----------------------------------------------------- > > Key: OVIRT-1919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > we needed to re-merge a change from github and did not know how to do it. > looking at the documentation it either does not exist or not documented. > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… > I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Barak Korren (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-886: ------------------------------- Status: To Do (was: In Progress) > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Barak Korren (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Barak Korren reopened OVIRT-886: -------------------------------- > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2140) enforce SSL on resources.ovirt.org
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2140?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2140: ---------------------------------- [~ederevea] do we still need to do this? what are the risks? > enforce SSL on resources.ovirt.org > ---------------------------------- > > Key: OVIRT-2140 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2140 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > SSL was enabled on Resources with OVIRT-1472, this ticket is to transform the non-SSL virtual hosts into redirects to the SSL version -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2138) Revert "open external repos for master until centos 7.5 calms down"
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2138?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2138: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Revert "open external repos for master until centos 7.5 calms down" > ------------------------------------------------------------------- > > Key: OVIRT-2138 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2138 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > I created the ticket but need to make sure it passes CI before merging: > https://gerrit.ovirt.org/#/c/91936/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2041) Setup CI mirrors for EL7/ppc64le
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2041?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2041: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) I don't recall any significant errors due to mirroring on PPC64 that required us mirroing repos, we have limited space on the mirror server, so I'd rather not add something we don't need. > Setup CI mirrors for EL7/ppc64le > -------------------------------- > > Key: OVIRT-2041 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2041 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: CI Mirrors > Reporter: Barak Korren > Assignee: infra > Labels: ppc64le > > We've been having trouble with PPC64LE slaves due to packaging issues, its desirable to setup CI mirrors that will protect the CI system from such issues in the future -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1536) Documentation about the change-queue flow
by Dafna Ron (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1536?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-1536: ---------------------------------- I did a diagram (two actually, simple one and a more detailed one) but I think that this is the best way to document cq rather then a written doc > Documentation about the change-queue flow > ----------------------------------------- > > Key: OVIRT-1536 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1536 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue, Documentation > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > Add some reference documentation about the change-queue flow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1919) missing documentation on ci re-merge please in github
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1919?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1919: ---------------------------------- [~dron] can you add the relevant docs that we need for it if we don’t have it already? > missing documentation on ci re-merge please in github > ----------------------------------------------------- > > Key: OVIRT-1919 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1919 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Dafna Ron > Assignee: infra > > we needed to re-merge a change from github and did not know how to do it. > looking at the documentation it either does not exist or not documented. > http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Using_STDCI_with_GitHub… > I am assuming that we can re-merge so opening a jira for the doc. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1868) Allow engineers to write Jenkinsfiles
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1868?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-1868: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) > Allow engineers to write Jenkinsfiles > ------------------------------------- > > Key: OVIRT-1868 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1868 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Roman Mohr > Assignee: infra > > Looks like standard-ci switched internally to use Jenkinsfiles. However it > would be very valuable for engineers, if they could just write their > Jenkinsfile, instead of all the usual standard-ci yamls/scripts. > With the Jenkinsfile the chroot based approach seems to be pretty obsolete, > if you allow people to use the docker agent for the Jenkinsfile. For > KubeVirt it would make standard-ci finally really valuable. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1867) Allow embedded secrets inside the source repo for CI
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1867?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-1867: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) KubeVirt moved to Prow, and AFAIU this feature isn't needed anymore on STDCI. > Allow embedded secrets inside the source repo for CI > ---------------------------------------------------- > > Key: OVIRT-1867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1867 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines), STDCI DSL > Reporter: Roman Mohr > Assignee: infra > Labels: credentials > > In order to improve the self-service capabilities of standard-ci it is > important for projects, that they can add their own secrets to projects (to > reach external services, e.g. docker hub, ...). > Travis has a very nice system which helps engineers there: > https://docs.travis-ci.com/user/encryption-keys/ > Basically the CI system needs to generate a public/private key pair for > every enabled git repo. The engineer simply fetches the public key via a > well know URL and encrypts the secrets. Then the encrypted secret can be > made part of the source repo. Before the tests are run the CI system > decrypts the secrets. Than can play together pretty well with Jenkinsfiles > too. > Benefit: > * Less manual intervention from CI team to add secrets to jobs > * Strengthen the config-in-code thinking -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1840) jobs freeze due to unresponsive docker
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1840?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-1840: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > jobs freeze due to unresponsive docker > -------------------------------------- > > Key: OVIRT-1840 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1840 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > > Quite often do I see jobs stuck at various stages for hours that seem related to docker. > Example: > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc26-x86_6… > There's multiple docker commands stuck on the slave (will post in the next comment) so it seems to be deadlocked. Opening ticket to investigate which step exactly is causing this and possible ways of resolving. The job in question doesn't even use docker so shouldn't suffer if this happens. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#29). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 66 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/29 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 29 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

[JIRA] (OVIRT-1554) Get rid of old 'create_rpms' jobs
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1554?page=com.atlassian.jira.… ] Eyal Edri closed OVIRT-1554. ---------------------------- Resolution: Fixed (was: Won't Do) > Get rid of old 'create_rpms' jobs > --------------------------------- > > Key: OVIRT-1554 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1554 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: re-factor, standard-ci > > '*create_rpms*' jobs are the old kind of jobs that we used to have before STD-CI. We still have many of those laying around. > Here is the list for the time of writing these lines: > # vdsm_any_create-rpms_manual > # mom_any_create-rpms_manual_old > # qemu_4.1_create-rpms-el7-x86_64_merged > # qemu_4.1_create-rpms-el7-ppc64le_merged > # qemu_4.1_create-rpms-el7-x86_64_created > # qemu_4.1_create-rpms-el7-ppc64le_created > # qemu_master_create-rpms-el7-x86_64_created > # slf4j_master_create-rpms-el6-x86_64_merged > # qemu_master_create-rpms-el7-ppc64le_created > # slf4j_master_create-rpms-el6-x86_64_created > # ioprocess_0.15_create-rpms-el7-x86_64_merged > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_merged > # ioprocess_0.15_create-rpms-el7-x86_64_created > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_created > # ovirt-reports_3.6_create-rpms-el6-x86_64_merged > # ovirt-reports_3.6_create-rpms-el7-x86_64_merged > # ovirt-wgt_master_create-rpms-fc25-x86_64_merged > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_merged > # ovirt-reports_3.6_create-rpms-el6-x86_64_created > # ovirt-reports_3.6_create-rpms-el7-x86_64_created > # ovirt-wgt_master_create-rpms-fc25-x86_64_created > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_created > # python-windows_4.1_create-rpms-el7-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_created > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_created > # ovirt-hosted-engine-ha_any_create-rpms_manual_old > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged > # python-windows_4.1_create-rpms-el7-x86_64_created > # python-windows_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_created > # py2exe-py2.7_master_create-rpms-fc25-x86_64_merged > # python-windows_4.1_create-rpms-fc24-x86_64_created > # pywin32-py2.7_master_create-rpms-el7-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_merged > # vcredist-x86_master_create-rpms-fc26-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged > # py2exe-py2.7_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_merged > # pywin32-py2.7_master_create-rpms-el7-x86_64_created > # pywin32-py2.7_master_create-rpms-fc25-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc26-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_created > # vcredist-x86_master_create-rpms-fc26-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-fc25-x86_64_merged > # python-windows_master_create-rpms-fc26-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc25-x86_64_created > # pywin32-py2.7_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged > # python-windows_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_created > # ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged > # jasperreports-server_master_create-rpms-el6-x86_64_merged > # jasperreports-server_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_created > # jasperreports-server_master_create-rpms-el6-x86_64_created > # jasperreports-server_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_merged > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_created > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_created > # tmp_ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_tagged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_merged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1554) Get rid of old 'create_rpms' jobs
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1554?page=com.atlassian.jira.… ] Eyal Edri reopened OVIRT-1554: ------------------------------ > Get rid of old 'create_rpms' jobs > --------------------------------- > > Key: OVIRT-1554 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1554 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: re-factor, standard-ci > > '*create_rpms*' jobs are the old kind of jobs that we used to have before STD-CI. We still have many of those laying around. > Here is the list for the time of writing these lines: > # vdsm_any_create-rpms_manual > # mom_any_create-rpms_manual_old > # qemu_4.1_create-rpms-el7-x86_64_merged > # qemu_4.1_create-rpms-el7-ppc64le_merged > # qemu_4.1_create-rpms-el7-x86_64_created > # qemu_4.1_create-rpms-el7-ppc64le_created > # qemu_master_create-rpms-el7-x86_64_created > # slf4j_master_create-rpms-el6-x86_64_merged > # qemu_master_create-rpms-el7-ppc64le_created > # slf4j_master_create-rpms-el6-x86_64_created > # ioprocess_0.15_create-rpms-el7-x86_64_merged > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_merged > # ioprocess_0.15_create-rpms-el7-x86_64_created > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_created > # ovirt-reports_3.6_create-rpms-el6-x86_64_merged > # ovirt-reports_3.6_create-rpms-el7-x86_64_merged > # ovirt-wgt_master_create-rpms-fc25-x86_64_merged > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_merged > # ovirt-reports_3.6_create-rpms-el6-x86_64_created > # ovirt-reports_3.6_create-rpms-el7-x86_64_created > # ovirt-wgt_master_create-rpms-fc25-x86_64_created > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_created > # python-windows_4.1_create-rpms-el7-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_created > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_created > # ovirt-hosted-engine-ha_any_create-rpms_manual_old > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged > # python-windows_4.1_create-rpms-el7-x86_64_created > # python-windows_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_created > # py2exe-py2.7_master_create-rpms-fc25-x86_64_merged > # python-windows_4.1_create-rpms-fc24-x86_64_created > # pywin32-py2.7_master_create-rpms-el7-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_merged > # vcredist-x86_master_create-rpms-fc26-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged > # py2exe-py2.7_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_merged > # pywin32-py2.7_master_create-rpms-el7-x86_64_created > # pywin32-py2.7_master_create-rpms-fc25-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc26-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_created > # vcredist-x86_master_create-rpms-fc26-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-fc25-x86_64_merged > # python-windows_master_create-rpms-fc26-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc25-x86_64_created > # pywin32-py2.7_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged > # python-windows_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_created > # ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged > # jasperreports-server_master_create-rpms-el6-x86_64_merged > # jasperreports-server_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_created > # jasperreports-server_master_create-rpms-el6-x86_64_created > # jasperreports-server_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_merged > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_created > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_created > # tmp_ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_tagged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_merged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1554) Get rid of old 'create_rpms' jobs
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1554?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-1554: ----------------------------- Status: Done (was: To Do) > Get rid of old 'create_rpms' jobs > --------------------------------- > > Key: OVIRT-1554 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1554 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: re-factor, standard-ci > > '*create_rpms*' jobs are the old kind of jobs that we used to have before STD-CI. We still have many of those laying around. > Here is the list for the time of writing these lines: > # vdsm_any_create-rpms_manual > # mom_any_create-rpms_manual_old > # qemu_4.1_create-rpms-el7-x86_64_merged > # qemu_4.1_create-rpms-el7-ppc64le_merged > # qemu_4.1_create-rpms-el7-x86_64_created > # qemu_4.1_create-rpms-el7-ppc64le_created > # qemu_master_create-rpms-el7-x86_64_created > # slf4j_master_create-rpms-el6-x86_64_merged > # qemu_master_create-rpms-el7-ppc64le_created > # slf4j_master_create-rpms-el6-x86_64_created > # ioprocess_0.15_create-rpms-el7-x86_64_merged > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_merged > # ioprocess_0.15_create-rpms-el7-x86_64_created > # ovirt-wgt_4.1_create-rpms-fc24-x86_64_created > # ovirt-reports_3.6_create-rpms-el6-x86_64_merged > # ovirt-reports_3.6_create-rpms-el7-x86_64_merged > # ovirt-wgt_master_create-rpms-fc25-x86_64_merged > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_merged > # ovirt-reports_3.6_create-rpms-el6-x86_64_created > # ovirt-reports_3.6_create-rpms-el7-x86_64_created > # ovirt-wgt_master_create-rpms-fc25-x86_64_created > # py2exe-py2.7_4.1_create-rpms-fc24-x86_64_created > # python-windows_4.1_create-rpms-el7-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-el7-x86_64_created > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_merged > # vcredist-x86_4.1_create-rpms-fc24-x86_64_created > # ovirt-hosted-engine-ha_any_create-rpms_manual_old > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged > # python-windows_4.1_create-rpms-el7-x86_64_created > # python-windows_4.1_create-rpms-fc24-x86_64_merged > # pywin32-py2.7_4.1_create-rpms-fc24-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el6-x86_64_created > # ovirt-vmconsole_3.6_create-rpms-el7-x86_64_created > # py2exe-py2.7_master_create-rpms-fc25-x86_64_merged > # python-windows_4.1_create-rpms-fc24-x86_64_created > # pywin32-py2.7_master_create-rpms-el7-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_merged > # vcredist-x86_master_create-rpms-fc26-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged > # py2exe-py2.7_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_merged > # pywin32-py2.7_master_create-rpms-el7-x86_64_created > # pywin32-py2.7_master_create-rpms-fc25-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc26-x86_64_merged > # vcredist-x86_master_create-rpms-fc25-x86_64_created > # vcredist-x86_master_create-rpms-fc26-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el6-x86_64_created > # ovirt-host-deploy_3.6_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-el7-x86_64_created > # python-windows_master_create-rpms-fc25-x86_64_merged > # python-windows_master_create-rpms-fc26-x86_64_merged > # pywin32-py2.7_master_create-rpms-fc25-x86_64_created > # pywin32-py2.7_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged > # python-windows_master_create-rpms-fc25-x86_64_created > # python-windows_master_create-rpms-fc26-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el6-x86_64_created > # ovirt-log-collector_3.6_create-rpms-el7-x86_64_created > # ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged > # ovirt-engine-sdk-java_3.6_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged > # jasperreports-server_master_create-rpms-el6-x86_64_merged > # jasperreports-server_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_created > # jasperreports-server_master_create-rpms-el6-x86_64_created > # jasperreports-server_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_merged > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly10_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly10_master_create-rpms-fc26-x86_64_created > # nsis-simple-service-plugin_4.1_create-rpms-fc24-x86_64_created > # tmp_ovirt-hosted-engine-ha_master_create-rpms-el7-x86_64_tagged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_merged > # nsis-simple-service-plugin_master_create-rpms-fc25-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_merged > # ovirt-engine-wildfly-overlay10_4.1_create-rpms-fc24-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-el6-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-el7-x86_64_created > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_merged > # ovirt-engine-wildfly-overlay10_master_create-rpms-fc25-x86_64_created -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1545) create unix group for infra admins on systems
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1545?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-1545: -------------------------------- Assignee: Shlomi Zidmi (was: infra) > create unix group for infra admins on systems > --------------------------------------------- > > Key: OVIRT-1545 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1545 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Shlomi Zidmi > > To ease access to shared files, we should create a group and add all admins to it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1536) Documentation about the change-queue flow
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1536?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1536: ---------------------------------- [~dron] you did some docs on it recently with a document and diagram no? > Documentation about the change-queue flow > ----------------------------------------- > > Key: OVIRT-1536 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1536 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue, Documentation > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > Add some reference documentation about the change-queue flow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[CQ]: 101482, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Jul '19

04 Jul '19

A system test invoked by the "ovirt-master" change queue including change 101482,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 101463,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 101463,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/101482/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/101463/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14848/

1 0

[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1396?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1396: ---------------------------------- [~bkorren(a)redhat.com] still relevant? > Add a new 'test-system-artifacts' Standard-CI stage > --------------------------------------------------- > > Key: OVIRT-1396 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > An order to allow building and testing processes for containers to be triggered after package that are needed for them are built, we will introduce the "{{test-system-artifacts}}" standard-CI stage. > This stage will be invoked from the 'experimental' or 'change-queue-tester' pipelines jost like the existing OST-based flows. > In order to provide package and repo information to the std-CI script invoked by this stage we well need to implement OVIRT-1391 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira.p… ] Eyal Edri commented on OVIRT-914: --------------------------------- [~bkorren(a)redhat.com] is this still planned/needed? > Better arch support for mock_runner.sh > -------------------------------------- > > Key: OVIRT-914 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-914 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock_runner.sh, standard-ci > > We managed to us "{{mock_runner.sh}}" in multi-arch so far because it was flexible enough to allow us to select the chroot file. > The issue is that mock_runner does not actually *know* the arch we are running on so we can`t:: > * do different mounts per-arch > * install different packages per-arch > * have different {{check_*}} scripts per-arch -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Eyal Edri updated OVIRT-886: ---------------------------- Status: Done (was: To Do) > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2635) Puppet failed to configure the sudoers file
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2635?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2635: ---------------------------------- [~gbenhaim(a)redhat.com] is this still relevant? > Puppet failed to configure the sudoers file > ------------------------------------------- > > Key: OVIRT-2635 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2635 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gal Ben Haim > Assignee: infra > > We are affected by https://bugs.centos.org/view.php?id=15567 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2187) Create master suite based on FC 28
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2187?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2187: ----------------------------- Resolution: Won't Do Status: Done (was: To Do) Doesn't seem there is need/resources for this effort ATM. Its more likely we'll run oVirt 4.4 on CentOS 8 sooner. > Create master suite based on FC 28 > ---------------------------------- > > Key: OVIRT-2187 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2187 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-1956) manual job upgrade options/table are messy
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1956?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-1956: ---------------------------------- [~amarchuk] this looks like a text update, can [~szidmi] handle it? > manual job upgrade options/table are messy > ------------------------------------------ > > Key: OVIRT-1956 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1956 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Yedidyah Bar David > Assignee: infra > > Hi, > This was originally reported as [1]. > It's not completely clear what each choice of 'ENGINE_VERSION' and > 'SUITE_TYPE' runs. We should clarify that, add to the table missing > information if needed, including noting somehow combinations that > should not work, if any (e.g. upgrade from 4.0 to 4.2 or master). > In addition to what I wrote in [1], I now checked and saw that a patch > [2] for 4.1 made the change-queue run [3]: > - basic-suite > - upgrade-from-prevrelease - this caused upgrade from 4.0 to 4.1 > - upgrade-from-release - this caused upgrade from 4.1 (released?) to > 4.1 (tested) > Which looks just fine to me, but if that's also supported by the > manual job, it's very hard to guess from the table. > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1552703 > [2] https://gerrit.ovirt.org/89556 > [3] http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1746/artifact/ex… > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2617) Allow rerunning only failed test lanes
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2617?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2617: ----------------------------- Resolution: Fixed Status: Done (was: To Do) This was achived in the end by moving to Prow. There are no plans to add it to STD-CI at this stage. > Allow rerunning only failed test lanes > -------------------------------------- > > Key: OVIRT-2617 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2617 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roman Mohr > Assignee: infra > > Hi, > In KubeVirt we run a lot of differnent test lanes. Even if our tests are > written in a good way and if the underlying CI infra is stable and fast, > there will always be cases where for-whatever reason one or two tests can > fail out of hundreds in a lane. > It would be very helpful if we could have a /retest command or something > similar where only failed lanes are re-run. That would be similar to how it > is handled in Kubernetes. > Right now it is an all-or-nothing thing. > What I would expect, is that it is still possible to see the test history > somewhere then (e.g. the first two attempts where it failed and then the > third one where it succeeds). > Best Regards, > Roman -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#28). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 65 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/28 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 28 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

[JIRA] (OVIRT-2709) Please create new repositories on ovirt github for new Ansible role
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2709?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2709: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Please create new repositories on ovirt github for new Ansible role > ------------------------------------------------------------------- > > Key: OVIRT-2709 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2709 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shirly Radco > Assignee: infra > > Please create following repositories: > ovirt-ansible-origin-on-ovirt > And please assign sradco, rgolan, machacekondra and mwperina as administrators. > Thanks. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2714: ---------------------------------- [~gbenhaim(a)redhat.com] [~dbelenky(a)redhat.com] what do we need to do in order to move the manual OST job to use containers? > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

[JIRA] (OVIRT-2725) Build artifacts failed - not enough free space on file system
by Eyal Edri (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2725?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2725: ----------------------------- Resolution: Duplicate Status: Done (was: To Do) we have open tickets on the s390x slave already > Build artifacts failed - not enough free space on file system > ------------------------------------------------------------- > > Key: OVIRT-2725 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2725 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Nir Soffer > Assignee: infra > > I had this failure in yum install: > [2019-05-12T14:54:55.706Z] Error Summary > [2019-05-12T14:54:55.706Z] ------------- > [2019-05-12T14:54:55.706Z] Disk Requirements: > [2019-05-12T14:54:55.706Z] At least 70MB more space needed on the / > filesystem. > Build: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Trying build again, hopefully will get a slave with more space... > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#27). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 66 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/27 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 27 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#26). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 67 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/26 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 26 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

[JIRA] (OVIRT-2748) Re: "Dev Role" on Jenkins
by Anton Marchukov (oVirt JIRA) 04 Jul '19

04 Jul '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2748?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2748: ---------------------------------------- [~germano(a)redhat.com] can you confirm it is working for you now? > Re: "Dev Role" on Jenkins > ------------------------- > > Key: OVIRT-2748 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2748 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Dafna Ron > Assignee: Daniel Belenky > > Adding infra-support as this needs a ticket > On Mon, Jul 1, 2019 at 7:07 AM Germano Veit Michel <germano(a)redhat.com> > wrote: > > Hi, > > > > I would like to be able to manually trigger OST. According to [1] I might > > be missing the "Dev Role" as I cannot see the "*build with parameters*" > > menu. > > > > Could you please check if I have permissions? > > > > [1] > > https://ovirt-system-tests.readthedocs.io/en/latest/CI/developers_info/inde… > > > > Thanks, > > Germano > > _______________________________________________ > > Infra mailing list -- infra(a)ovirt.org > > To unsubscribe send an email to infra-leave(a)ovirt.org > > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > List Archives: > > https://lists.ovirt.org/archives/list/infra@ovirt.org/message/YEEUZ6B6WJUNV… > > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100105)

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/256 ) Change subject: Add gate-triggering Zuul job ...................................................................... Patch Set 25: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 25 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org> Gerrit-Comment-Date: Thu, 04 Jul 2019 09:56:57 +0000 Gerrit-HasComments: No

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#25). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 79 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/25 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 25 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/256 ) Change subject: Add gate-triggering Zuul job ...................................................................... Patch Set 24: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 24 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org> Gerrit-Comment-Date: Thu, 04 Jul 2019 09:30:57 +0000 Gerrit-HasComments: No

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/256 ) Change subject: Add gate-triggering Zuul job ...................................................................... Patch Set 24: ci test please -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 24 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org> Gerrit-Comment-Date: Thu, 04 Jul 2019 09:24:05 +0000 Gerrit-HasComments: No

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#24). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 80 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/24 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 24 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#23). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 78 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/23 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 23 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#22). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 78 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/22 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 22 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0

Change in stage-stdci1[master]: Add gate-triggering Zuul job
by review＠gerrit-staging.phx.ovirt.org 04 Jul '19

04 Jul '19

From Barak Korren <bkorren(a)redhat.com>: Hello Jenkins CI, Zuul CI, I'd like you to reexamine a change. Please visit https://gerrit-staging.phx.ovirt.org/256 to look at the new patch set (#21). Change subject: Add gate-triggering Zuul job ...................................................................... Add gate-triggering Zuul job Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Signed-off-by: Barak Korren <bkorren(a)redhat.com> --- M .zuul.yaml A automation/playbooks/trigger_gate_job.yaml 2 files changed, 78 insertions(+), 2 deletions(-) git pull ssh://gerrit-staging.phx.ovirt.org:29418/stage-stdci1 refs/changes/56/256/21 -- To view, visit https://gerrit-staging.phx.ovirt.org/256 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: stage-stdci1 Gerrit-Branch: master Gerrit-MessageType: newpatchset Gerrit-Change-Id: Ic2892757a81c5c0705bde6db77bdc546efe49faf Gerrit-Change-Number: 256 Gerrit-PatchSet: 21 Gerrit-Owner: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Barak Korren <bkorren(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Reviewer: Zuul CI <zuul(a)ovirt.org>

1 0