[JIRA] (OVIRT-1584) Create Branch and User fields in ansible_suite job

Tuesday, 8 August 2017

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

------------=_1502200776-12480-346
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

    [
https://ovirt-jira.atlassian.net/browse/OVIRT-1584?page=com.atlassian.jir...
] 

eyal edri commented on OVIRT-1584:
----------------------------------

Hi Ondra, 
It's not really possible to add what you're asking with the current way OST works
in CI, since the OST job isn't building ( and shouldn't ) build any project, just
test it.

The way to test PRs in Jenkins is to use the manual job [1] and custom RPMs, usually built
by the 'build on demand' feature.
The blog [2] described how to do it, though we'll need to check if we support
'build on demand' for GitHub projects like ovirt-ansible.

We'll need to add the 'ansible' suite the the list of suites you can test
using the manual job and to verify you can build from a patch, so you'll have a custom
yum repo to provide the job to test.

[~dbelenky(a)redhat.com] can you help adding the ansible suite to the list of suites
available in the manual OST Job?
[~bkorren(a)redhat.com] do we support 'build on demand' for GitHub projects? if not,
then i guess 'check-patch' job can be used if the RPM is built there

[1] http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-tes...
[2] https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-rescue/

...
 Create Branch and User fields in ansible_suite job
 --------------------------------------------------

                 Key: OVIRT-1584
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1584
             Project: oVirt - virtualization made easy
          Issue Type: Bug
          Components: OST, oVirt CI
            Reporter: Ondra Machacek
            Assignee: infra

 I would like to have following fields in ansible job[1].
  - branch (default: devel)
  - username (default: ansible)
 So in OST[2], we can define which branch+ from which git repo, should be fetched,
 with this we can test PRs.
 [1] http://jenkins.ovirt.org/job/system-tests_ansible-suite-master/
 [2] https://github.com/oVirt/ovirt-system-tests/blob/master/run_suite.sh#L212
 [~lbednar] 

--
This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100058)

------------=_1502200776-12480-346
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[
https://ovirt-jira.atlassian.net/browse/OVIRT-1584?page=com.atlassian.jir...
]</pre>
<h3>eyal edri commented on OVIRT-1584:</h3>
<p>Hi Ondra, It's not really possible to add what you're asking with the
current way OST works in CI, since the OST job isn't building ( and shouldn't )
build any project, just test it.</p>
<p>The way to test PRs in Jenkins is to use the manual job [1] and custom RPMs,
usually built by the &lsquo;build on demand&rsquo; feature. The blog [2] described
how to do it, though we'll need to check if we support &lsquo;build on
demand&rsquo; for GitHub projects like ovirt-ansible.</p>
<p>We'll need to add the &lsquo;ansible&rsquo; suite the the list of
suites you can test using the manual job and to verify you can build from a patch, so
you'll have a custom yum repo to provide the job to test.</p>
<p&gt;[~dbelenky(a)redhat.com] can you help adding the ansible suite to the list of
suites available in the manual OST Job? [~bkorren(a)redhat.com] do we support
&lsquo;build on demand&rsquo; for GitHub projects? if not, then i guess
&lsquo;check-patch&rsquo; job can be used if the RPM is built there</p>
<p>[1] <a
href="http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt...
[2] <a
href="https://www.ovirt.org/blog/2017/01/ovirt-system-tests-to-the-r...
<blockquote><h3>Create Branch and User fields in ansible_suite job</h3>
<pre>     Key: OVIRT-1584
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1584
 Project: oVirt - virtualization made easy
         Issue Type: Bug
         Components: OST, oVirt CI
Reporter: Ondra Machacek
Assignee: infra</pre>
<p>I would like to have following fields in ansible job[1].</p>
<pre>- branch (default: devel)
- username (default: ansible)</pre>
<p>So in OST[2], we can define which branch+ from which git repo, should be fetched,
with this we can test PRs. [1] <a
href="http://jenkins.ovirt.org/job/system-tests_ansible-suite-master...
[2] <a
href="https://github.com/oVirt/ovirt-system-tests/blob/master/run_su...
[~lbednar]</p></blockquote>
<p>&mdash; This message was sent by Atlassian JIRA
(v1001.0.0-SNAPSHOT#100058)</p>

------------=_1502200776-12480-346--

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011