June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2234) Encapsulate tag-on-release option in queue_build_args
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2234?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2234: ---------------------------------- Epic Link: OVIRT-1717 > Encapsulate tag-on-release option in queue_build_args > ----------------------------------------------------- > > Key: OVIRT-2234 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2234 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue, Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > In order to support reverse tagging in CQ, we have to encapsulate the 'tag-on-release' option when creating a new change object. > *Acceptance criteria:* > * Read the configuration from the DSL's output. > * Pass the configuration to the relevant CQ code when generating the change object. > * Change object needs to be able to handle such field and store it's data properly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2234) Encapsulate tag-on-release option in queue_build_args
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

Daniel Belenky created OVIRT-2234: ------------------------------------- Summary: Encapsulate tag-on-release option in queue_build_args Key: OVIRT-2234 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2234 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Change Queue, Standard CI (Pipelines) Reporter: Daniel Belenky Assignee: infra In order to support reverse tagging in CQ, we have to encapsulate the 'tag-on-release' option when creating a new change object. *Acceptance criteria:* * Read the configuration from the DSL's output. * Pass the configuration to the relevant CQ code when generating the change object. * Change object needs to be able to handle such field and store it's data properly. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2233) Add 'tag-on-release' configuration to STDCI DSL
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2233?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2233: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Add 'tag-on-release' configuration to STDCI DSL > ----------------------------------------------- > > Key: OVIRT-2233 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2233 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > As a project maintainer, I want to have the ability to tell STDCI whether to tag every release of my project or not and to specify a custom tag so that I will have full control of the release process. > *Acceptance criteria:* > * Verify the structure of tag-on-release option > * Pass the configuration along with the global options via the matching formatter (pipeline_dict formatter) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2233) Add 'tag-on-release' configuration to STDCI DSL
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2233?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2233: ---------------------------------- Epic Link: OVIRT-1717 > Add 'tag-on-release' configuration to STDCI DSL > ----------------------------------------------- > > Key: OVIRT-2233 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2233 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Daniel Belenky > Assignee: infra > > As a project maintainer, I want to have the ability to tell STDCI whether to tag every release of my project or not and to specify a custom tag so that I will have full control of the release process. > *Acceptance criteria:* > * Verify the structure of tag-on-release option > * Pass the configuration along with the global options via the matching formatter (pipeline_dict formatter) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2233) Add 'tag-on-release' configuration to STDCI DSL
by Daniel Belenky (oVirt JIRA) 24 Jun '18

24 Jun '18

Daniel Belenky created OVIRT-2233: ------------------------------------- Summary: Add 'tag-on-release' configuration to STDCI DSL Key: OVIRT-2233 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2233 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Daniel Belenky Assignee: infra As a project maintainer, I want to have the ability to tell STDCI whether to tag every release of my project or not and to specify a custom tag so that I will have full control of the release process. *Acceptance criteria:* * Verify the structure of tag-on-release option * Pass the configuration along with the global options via the matching formatter (pipeline_dict formatter) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1983) Switch to using JJB >= 2.0.6
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1983?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1983: ----------------------------------- Assignee: Barak Korren (was: infra) > Switch to using JJB >= 2.0.6 > ---------------------------- > > Key: OVIRT-1983 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1983 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: Barak Korren > > Version 2.0.6 is the latest released version of JJB at the time of this writing. We've been using a very old development version of JJB (1.4.1.dev50) for a long time and its about time we upgraded. Other then that the post 2.0.0 has one major feature which is Jinja2 support which may be very useful for us. > In order to upgrade, we probably need to implement OVIRT-1466 first. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 92435, 1 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Jun '18

24 Jun '18

A system test invoked by the "ovirt-master" change queue including change 92435,1 (otopi) failed. However, this change seems not to be the root cause for this failure. Change 91908,6 (otopi) 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 91908,6 (otopi) 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/92435/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91908/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8326/

1 0

[JIRA] (OVIRT-2231) QEMU can't access "/home/jenkins/*" on FC28 slaves.
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2231?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2231: ------------------------------------- This should probably be done from {{globals_setup.sh}} so setting component as "Jenkins Slaves" > 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: Jenkins Slaves > 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)

1 0

[JIRA] (OVIRT-2231) QEMU can't access "/home/jenkins/*" on FC28 slaves.
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2231?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2231: -------------------------------- Component/s: (was: Lago) Jenkins Slaves > 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: Jenkins Slaves > 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)

1 0

[JIRA] (OVIRT-1144) Make projects support more than one CI system
by Barak Korren (oVirt JIRA) 24 Jun '18

24 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1144?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1144: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We're not going to support other CI systems. > Make projects support more than one CI system > --------------------------------------------- > > Key: OVIRT-1144 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1144 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Eyal Edri > Assignee: infra > > Today we use 'automation' dir for running all standard CI flows on oVirt CI. > We need to take into consideration future projects will use multiple CI systems and be a part of multiple projects. > So a question is raised on how will the structure of dirs/files served in oVirt will look like. > One suggestion was to use .ovirtci which will translate to all the needs the oVirt CI will need. > There can be other options, this is the place to discuss them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0