[JIRA] (OVIRT-1825) Document the process for setting up a "downstream" STDCI system

3 Jan 2018


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

------------=_1514960598-31600-208
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Barak Korren reassigned OVIRT-1825:
-----------------------------------

    Assignee: Barak Korren  (was: infra)
...
Document the process for setting up a "downstream" STDCI system
---------------------------------------------------------------
Key: OVIRT-1825
                URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1825
            Project: oVirt - virtualization made easy
         Issue Type: Improvement
         Components: oVirt CI
           Reporter: Barak Korren
           Assignee: Barak Korren
             Labels: documentation, standard-ci
With the introduction of so called "upstream source" dependencies, it had become possible to use the '{{jenkins}}' repo and the STDCI code in it as a library for building STDCI-compatible jenkins servers.
This process had been successfully used to setup the RHV CI system inside Red Hat.
The processes of setting up a non-oVirt STDCI server should be documented to make it accessible for others.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)

------------=_1514960598-31600-208
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1825?page=com.atlassian.jira.p... ]</pre>
<h3>Barak Korren reassigned OVIRT-1825:</h3>
<pre>Assignee: Barak Korren  (was: infra)</pre>
<blockquote><h3>Document the process for setting up a “downstream” STDCI system</h3>
<pre>     Key: OVIRT-1825
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1825
 Project: oVirt - virtualization made easy
         Issue Type: Improvement
         Components: oVirt CI
Reporter: Barak Korren
Assignee: Barak Korren
  Labels: documentation, standard-ci</pre>
<p>With the introduction of so called “upstream source” dependencies, it had become possible to use the ‘{{jenkins}}’ repo and the STDCI code in it as a library for building STDCI-compatible jenkins servers. This process had been successfully used to setup the RHV CI system inside Red Hat. The processes of setting up a non-oVirt STDCI server should be documented to make it accessible for others.</p></blockquote>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p>

<img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3t..." 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>

------------=_1514960598-31600-208--

Barak Korren (oVirt JIRA)

tags

participants (1)