<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]</pre>
<h3>Barak Korren updated OVIRT-1882:</h3>
<pre>Epic Link: OVIRT-400</pre>
<blockquote><h3>Figure out how to integrate Jenkins with beaker</h3>
<pre> Key: OVIRT-1882
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Jenkins Master
Reporter: Barak Korren
Assignee: infra
Labels: beaker</pre>
<p>If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins. One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs. It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed.</p></blockquote>
<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-2BJ33BSM3tuiUfRTk64K-2BOjGpF-2BuMzoJRRB1ifzZIErtIxTccLy521zz7OxZViB5mnpbbwYJFz6flgevXOzUJVH-2FqBqvcqqqKIp3p4OcyDFOsRwvaLk1r7X8JpLEbbYtQ-2F8se-2FAoG3NqMy6MEF960fM4WCfArIPipDAxV3I9QtDxwIZkeNWD9yApPsdJra3V4NT7hIOoTif46hN9A2Na-2BIseHngSSOzrSPo87Xs5dlTOpbBqbUpQFNGPq7wxrnGIxLf3j-2Fe5tALjjZ8Zmansiw-2FczYXb1SmfNmpO4Lebl0CGBXqKPltdcr0QHuvBs1LuJ7Dzyy0Xe26OhV-2FkNDtWQb0fXhxtoaZV7QSz9HdaAv4-2Fy5nv6kZCqPbHa2iVQ2b5vnXGTcxqY8BeqajnedVA60lamFugZ2mHJR9PRsBDsxT83" 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>