[JIRA] (OVIRT-1884) Scale up to multipile Jenkins masters

7 Feb 2018

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

------------=_1517996808-26764-286
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Barak Korren created OVIRT-1884:
-----------------------------------

             Summary: Scale up to multipile Jenkins masters
                 Key: OVIRT-1884
                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884
             Project: oVirt - virtualization made easy
          Issue Type: Improvement
          Components: Jenkins Master
            Reporter: Barak Korren
            Assignee: infra

There are several reasons why we would like to enable scaling up to multiple Jenkins masters:
* We may reach a point where a single jenkins master will simple not be able to cope with the workload we have - this is especially true as we increase our use of heavy features like pipelines and blue ocean.
* If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance.
*  As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance.

This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one.

--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100079)

------------=_1517996808-26764-286
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<h3>Barak Korren created OVIRT-1884:</h3>
<pre>   Summary: Scale up to multipile Jenkins masters
       Key: OVIRT-1884
       URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884
   Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Jenkins Master
  Reporter: Barak Korren
  Assignee: infra</pre>
<p>There are several reasons why we would like to enable scaling up to multiple Jenkins masters:</p>
<ul><li><p>We may reach a point where a single jenkins master will simple not be able to cope with the workload we have – this is especially true as we increase our use of heavy features like pipelines and blue ocean.</p></li>
<li><p>If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance.</p></li>
<li><p>As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance.</p></li></ul>
<p>This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one.</p>
<p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</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>

------------=_1517996808-26764-286--

Barak Korren (oVirt JIRA)

tags

participants (1)