[JIRA] (OVIRT-1629) Automation yaml

4 Sep 2017

      This is a multi-part message in MIME format...

------------=_1504532920-25723-154
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Daniel Belenky created OVIRT-1629:
-------------------------------------

             Summary: Automation yaml
                 Key: OVIRT-1629
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1629
             Project: oVirt - virtualization made easy
          Issue Type: New Feature
            Reporter: Daniel Belenky
            Assignee: infra

As part of the efforts of moving to std ci v2, we want to have the ability for projects to specify everything that currently is under the automation dir in a +single yaml.+
The config file will include all the metadata needed to generate std ci jobs.
We can split everything that is configurable under *automation* dir currently into two groups: _categories, options_
where categories are the *distro, arch, stage, substabe* and the options are actually the specific configuration for every category: *packages, repos, yumrepos, environment, runtime_requirements, script, ...*.

Syntax example:
{code:java}
arch:
  - x86_64
distro:
  - el7:
    arch:
      - ppc64le
  - fc26
stage:
  - check-patch:
      substage:
        - test
  - build-artifacts:
      arch:
        - ppc64le:
            distro:
              - fc24
substages:
  - build
  - test
{code}

--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)

------------=_1504532920-25723-154
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<h3>Daniel Belenky created OVIRT-1629:</h3>
<pre>   Summary: Automation yaml
       Key: OVIRT-1629
       URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1629
   Project: oVirt - virtualization made easy
Issue Type: New Feature
  Reporter: Daniel Belenky
  Assignee: infra</pre>
<p>As part of the efforts of moving to std ci v2, we want to have the ability for projects to specify everything that currently is under the automation dir in a +single yaml.+ The config file will include all the metadata needed to generate std ci jobs. We can split everything that is configurable under <strong>automation</strong> dir currently into two groups: <em>categories, options</em> where categories are the <strong>distro, arch, stage, substabe</strong> and the options are actually the specific configuration for every category: <strong>packages, repos, yumrepos, environment, runtime_requirements, script, …</strong>.</p>
<p>Syntax example: {code:java} arch:</p>
<pre>- x86_64</pre>
<p>distro:</p>
<pre>- el7:
  arch:
    - ppc64le
- fc26</pre>
<p>stage:</p>
<pre>  - check-patch:
      substage:
        - test
  - build-artifacts:
      arch:
        - ppc64le:
distro:
  - fc24</pre>
<p>substages:</p>
<pre>- build
- test</pre>
<p>{code}</p>
<p>— This message was sent by Atlassian {0} (v1001.0.0-SNAPSHOT#100059)</p>

<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzY..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/>
</body></html>

------------=_1504532920-25723-154--

Daniel Belenky (oVirt JIRA)

tags

participants (1)