- Infra - oVirt List Archives

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Description: 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. h3. Acceptance criteria: # The only JJB YAML needed to be written on a per-project basis for full support of all STDCI features is few details to basically enable STDCI support for the project # For most projects the code to be added should be one line with just the project name was: 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. > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Epic > 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. > h3. Acceptance criteria: > # The only JJB YAML needed to be written on a per-project basis for full support of all STDCI features is few details to basically enable STDCI support for the project > # For most projects the code to be added should be one line with just the project name -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Epic Name: Automate standard-CI job creation > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Epic > 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 (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Issue Type: Epic (was: Improvement) > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Epic > 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 (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Epic Link: (was: OVIRT-400) > Automate standard-CI job creation > --------------------------------- > > Key: OVIRT-1013 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1013 > Project: oVirt - virtualization made easy > Issue Type: Epic > 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 (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1013) Automate standard-CI job creation
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1013?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1013: -------------------------------- Summary: Automate standard-CI job creation (was: Automate standard-CI job creation (V2)) > Automate standard-CI job creation > --------------------------------- > > 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 (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1679) Move Lago to use the STDCI pipelines
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1679?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1679: -------------------------------- Epic Link: OVIRT-2175 (was: OVIRT-400) > Move Lago to use the STDCI pipelines > ------------------------------------ > > Key: OVIRT-1679 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1679 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Lago, oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue, github, jenkins, lago, standard-ci > > Because of work on OVIRT-1522, OVIRT-1599, we now have new pipeline jobs for GitHub projects. OVIRT-1486 and OVIRT-1534 gave us the ability to create change queues for GitHub projects. This is time to seriosly consider moving Lago from its old lago-specific STDCI clone to the general STDCI/CQ scheme. > Once we do that, we can also remove all the templates that are only used by Lago ATM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1679) Move Lago to use the STDCI pipelines
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1679?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1679: -------------------------------- Epic Link: OVIRT-2175 (was: OVIRT-400) > Move Lago to use the STDCI pipelines > ------------------------------------ > > Key: OVIRT-1679 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1679 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Lago, oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue, github, jenkins, lago, standard-ci > > Because of work on OVIRT-1522, OVIRT-1599, we now have new pipeline jobs for GitHub projects. OVIRT-1486 and OVIRT-1534 gave us the ability to create change queues for GitHub projects. This is time to seriosly consider moving Lago from its old lago-specific STDCI clone to the general STDCI/CQ scheme. > Once we do that, we can also remove all the templates that are only used by Lago ATM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2182) Create timed jobs
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2182?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2182: -------------------------------- Description: The timed jobs should use fc28 mock, so we will also test ovirt engine SDK. > Create timed jobs > ----------------- > > Key: OVIRT-2182 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2182 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Gal Ben Haim > Assignee: infra > > The timed jobs should use fc28 mock, so we will also test ovirt engine SDK. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2182) Create timed jobs
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

Gal Ben Haim created OVIRT-2182: ----------------------------------- Summary: Create timed jobs Key: OVIRT-2182 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2182 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: Gal Ben Haim Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2181) Release lago-ovirt for fc28
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

Gal Ben Haim created OVIRT-2181: ----------------------------------- Summary: Release lago-ovirt for fc28 Key: OVIRT-2181 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2181 Project: oVirt - virtualization made easy Issue Type: Sub-task Components: OST Reporter: Gal Ben Haim Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0