[JIRA] (OVIRT-1629) Automation yaml
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1629?page=com.atlassian.jir... ]
Daniel Belenky reassigned OVIRT-1629:
-------------------------------------
Assignee: Daniel Belenky (was: infra)
> 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: Daniel Belenky
>
> 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)
7 years, 2 months
[JIRA] (OVIRT-1629) Automation yaml
by Daniel Belenky (oVirt JIRA)
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-2BCmpYL..." 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--
7 years, 2 months
[JIRA] (OVIRT-1629) Automation yaml
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1629?page=com.atlassian.jir... ]
Daniel Belenky updated OVIRT-1629:
----------------------------------
Epic Link: OVIRT-400
> 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)
7 years, 2 months
[JIRA] (OVIRT-1628) CI build triggered only 15 minutes after push to gerrit
by Barak Korren (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1504521469-12532-126
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1628?page=com.atlassian.jir... ]
Barak Korren reassigned OVIRT-1628:
-----------------------------------
Assignee: Evgheni Dereveanchin (was: infra)
Component/s: Gerrit/git
Epic Link: OVIRT-403
Issue Type: Outage (was: By-EMAIL)
Priority: High (was: Medium)
> CI build triggered only 15 minutes after push to gerrit
> -------------------------------------------------------
>
> Key: OVIRT-1628
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1628
> Project: oVirt - virtualization made easy
> Issue Type: Outage
> Components: Gerrit/git
> Reporter: Yedidyah Bar David
> Assignee: Evgheni Dereveanchin
> Priority: High
>
> Hi all,
> See patchset 1 of [1].
> Sandro had a look and didn't notice any special load/backlog on jenkins
> that could explain that.
> Thanks,
> [1] https://gerrit.ovirt.org/81390
> --
> Didi
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
------------=_1504521469-12532-126
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1628?page=com.atlassian.jir... ]</pre>
<h3>Barak Korren reassigned OVIRT-1628:</h3>
<pre> Assignee: Evgheni Dereveanchin (was: infra)
Component/s: Gerrit/git
Epic Link: OVIRT-403
Issue Type: Outage (was: By-EMAIL)
Priority: High (was: Medium)</pre>
<blockquote><h3>CI build triggered only 15 minutes after push to gerrit</h3>
<pre> Key: OVIRT-1628
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1628
Project: oVirt - virtualization made easy
Issue Type: Outage
Components: Gerrit/git
Reporter: Yedidyah Bar David
Assignee: Evgheni Dereveanchin
Priority: High</pre>
<p>Hi all, See patchset 1 of [1]. Sandro had a look and didn't notice any special load/backlog on jenkins that could explain that. Thanks, [1] <a href="https://gerrit.ovirt.org/81390">https://gerrit.ovirt.org/81390</a> — Didi</p></blockquote>
<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-2BCmpYL..." 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>
------------=_1504521469-12532-126--
7 years, 2 months
[JIRA] (OVIRT-1628) CI build triggered only 15 minutes after push to gerrit
by Yedidyah Bar David (oVirt JIRA)
This is a multi-part message in MIME format...
------------=_1504518331-20857-120
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Yedidyah Bar David created OVIRT-1628:
-----------------------------------------
Summary: CI build triggered only 15 minutes after push to gerrit
Key: OVIRT-1628
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1628
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Yedidyah Bar David
Assignee: infra
Hi all,
See patchset 1 of [1].
Sandro had a look and didn't notice any special load/backlog on jenkins
that could explain that.
Thanks,
[1] https://gerrit.ovirt.org/81390
--
Didi
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
------------=_1504518331-20857-120
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
<html><body>
<h3>Yedidyah Bar David created OVIRT-1628:</h3>
<pre> Summary: CI build triggered only 15 minutes after push to gerrit
Key: OVIRT-1628
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1628
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Yedidyah Bar David
Assignee: infra</pre>
<p>Hi all,</p>
<p>See patchset 1 of [1].</p>
<p>Sandro had a look and didn't notice any special load/backlog on jenkins that could explain that.</p>
<p>Thanks,</p>
<p>[1] <a href="https://gerrit.ovirt.org/81390">https://gerrit.ovirt.org/81390</a> — Didi</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-2BCmpYL..." 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>
------------=_1504518331-20857-120--
7 years, 2 months
[JIRA] (OVIRT-1627) CI +1 marked only on previous patchset
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1627?page=com.atlassian.jir... ]
Evgheni Dereveanchin reassigned OVIRT-1627:
-------------------------------------------
Assignee: Evgheni Dereveanchin (was: infra)
> CI +1 marked only on previous patchset
> --------------------------------------
>
> Key: OVIRT-1627
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1627
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: Evgheni Dereveanchin
>
> Hi,
> In [1], patchset 6 was tested by CI while I pushed an update, 7, which only
> changed the commit message. It finished successfully, and only updated 6.
> Since 7 is a commit-message-only change, it was never marked or tested.
> I guess the code that marked +1 should also check all the newer patchsets
> and mark them too if they should inherit.
> Thanks,
> [1] https://gerrit.ovirt.org/77810
> --
> Didi
--
This message was sent by Atlassian {0}
(v1001.0.0-SNAPSHOT#100059)
7 years, 2 months