July 2017 - Infra - Ovirt List Archives

[JIRA] (OVIRT-1522) Re-implement standard-CI with pipelines (V2)

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1522?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1522: -------------------------------- Epic Link: OVIRT-400 > Re-implement standard-CI with pipelines (V2) > -------------------------------------------- > > Key: OVIRT-1522 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1522 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The Standard-CI system job in Jenkins are currently implemented using "Free-Style" Jenkins jobs, if we could re-implement them with Jenkins pipelines, if will enable us to use cleaner code and also have many features that may be to hard to implement with "Free-Style" jobs. > Tickets that specify features that will probably require using pipelines will linkt to this ticket as a blocker. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

8 years

1
0
0 / 0

[JIRA] (OVIRT-1522) Re-implement standard-CI with pipelines (V2)

by Barak Korren (oVirt JIRA)

Barak Korren created OVIRT-1522: ----------------------------------- Summary: Re-implement standard-CI with pipelines (V2) Key: OVIRT-1522 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1522 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra The Standard-CI system job in Jenkins are currently implemented using "Free-Style" Jenkins jobs, if we could re-implement them with Jenkins pipelines, if will enable us to use cleaner code and also have many features that may be to hard to implement with "Free-Style" jobs. Tickets that specify features that will probably require using pipelines will linkt to this ticket as a blocker. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

8 years

1
0
0 / 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation (V2)

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1013: -------------------------------- Summary: Automate standard-CI job creation (V2) (was: Automate standard-CI job creation) > Automate standard-CI job creation (V2) > -------------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > The premise of the CI standard is simple: The developers place simple script in the 'automation' directory, and The infa team take care of making Jenkins run it when it should. > But we haven't been able to fully deliver on this premise yet. Getting a project to work with the CI standard also takes writing some YAML in the 'Jenkins' repo. Even worse, this YAML needs to be maintained over time as new project branches get created, new platforms get targeted, etc. > The core reason behind having to write YAML, is that there are two technical details that we need to know in order to run the CI jobs, but are not specified in a way that allows detecting them automatically. Those details are: > 1. The platforms a certain project needs to be built and tested on. > 2. The branches of the project that CI needs to look at, and how do they map to an oVirt releases. > We need to specify a way to specify the details above in a way that will allow the CI system to automatically detect them. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

8 years

1
0
0 / 0

[JIRA] (OVIRT-1143) Standard CI V2

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1143: -------------------------------- Status: To Do (was: In Progress) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

8 years

1
0
0 / 0

[JIRA] (OVIRT-1143) Standard CI V2

by eedri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jir... ] eedri updated OVIRT-1143: ------------------------- Fix Version/s: (was: OVIRT-INFRA-FEB-2017) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

8 years

1
0
0 / 0

[JIRA] (OVIRT-1143) Standard CI V2

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jir... ] Barak Korren reopened OVIRT-1143: --------------------------------- > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > Fix For: OVIRT-INFRA-FEB-2017 > > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

8 years

1
0
0 / 0

[JIRA] (OVIRT-1143) Standard CI V2

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1143: -------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > Fix For: OVIRT-INFRA-FEB-2017 > > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

8 years

1
0
0 / 0

[JIRA] (OVIRT-1143) Standard CI V2

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1143: -------------------------------- Epic Link: OVIRT-400 (was: OVIRT-403) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eedri > Assignee: infra > Labels: standard-ci > Fix For: OVIRT-INFRA-FEB-2017 > > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

8 years

1
0
0 / 0

[JIRA] (OVIRT-1066) Fix error handling in the experimental flow Groovy script

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1066?page=com.atlassian.jir... ] Barak Korren updated OVIRT-1066: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) 'experimental' is going to be replaced by the change-queue. > Fix error handling in the experimental flow Groovy script > --------------------------------------------------------- > > Key: OVIRT-1066 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1066 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > Error handling is not done in a consistent manner in the Experimental flow Groovy script. Sometime exceptions are used, other times the 'currentBuild.result' variable is used and exceptions are actually suppressed. > This right way seems to be to use exceptions. Currently various things seem to be broken like properly marking that a build failed in the pipeline stage display plugin. -- This message was sent by Atlassian JIRA (v1000.1112.0#100055)

8 years

1
0
0 / 0

Change in ci-info_env-inject[master]: asdasdasdasd asd

by review＠gerrit-staging.phx.ovirt.org

>From Daniel Belenky <dbelenky(a)redhat.com>: Daniel Belenky has submitted this change and it was merged. ( https://gerrit-staging.phx.ovirt.org/63 ) Change subject: asdasdasdasd asd ...................................................................... asdasdasdasd asd Change-Id: Ia120f533910c1cfb1124e3a92f387e1c9be8cb30 --- M automation/check-patch.sh.el7 M automation/check-patch.sh.fc25 2 files changed, 12 insertions(+), 12 deletions(-) Approvals: Daniel Belenky: Looks good to me, approved; Verified; Passed CI tests -- To view, visit https://gerrit-staging.phx.ovirt.org/63 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-MessageType: merged Gerrit-Change-Id: Ia120f533910c1cfb1124e3a92f387e1c9be8cb30 Gerrit-PatchSet: 1 Gerrit-Project: ci-info_env-inject Gerrit-Branch: master Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>

8 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra July 2017