[ https://ovirt-jira.atlassian.net/browse/OVIRT-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barak Korren reassigned OVIRT-1884:

Assignee: Barak Korren  (was: infra)

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: Barak Korren
  Labels: scale

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)