[JIRA] (OVIRT-1465) Run JJB from 'check-merged' of 'jenkins' repo instead of its own job

26 Dec 2017


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

------------=_1514293711-12689-137
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35584#comment-35584 ] 

Barak Korren commented on OVIRT-1465:
-------------------------------------

[~eedri] no, both instances still use the deploy job.
...
Run JJB from 'check-merged' of 'jenkins' repo instead of its own job
--------------------------------------------------------------------
Key: OVIRT-1465
                URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465
            Project: oVirt - virtualization made easy
         Issue Type: Improvement
         Components: oVirt CI
           Reporter: Barak Korren
           Assignee: infra
             Labels: jenkins, jjb, standard-ci
Right not we have a custom job for running JJB after patches are merged to the 'jenkins' repo.
Once we can handle credentials in standard-CI we can move this functionality into the 'check-merged' job.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100075)

------------=_1514293711-12689-137
Content-Type: text/html; charset="UTF-8"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

<html><body>
<pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1465?page=com.atlassian.jira.p... ]</pre>
<h3>Barak Korren commented on OVIRT-1465:</h3>
<p>[~eedri] no, both instances still use the deploy job.</p>
<blockquote><h3>Run JJB from ‘check-merged’ of ‘jenkins’ repo instead of its own job</h3>
<pre>     Key: OVIRT-1465
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1465
 Project: oVirt - virtualization made easy
         Issue Type: Improvement
         Components: oVirt CI
Reporter: Barak Korren
Assignee: infra
  Labels: jenkins, jjb, standard-ci</pre>
<p>Right not we have a custom job for running JJB after patches are merged to the ‘jenkins’ repo. Once we can handle credentials in standard-CI we can move this functionality into the ‘check-merged’ job.</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>

------------=_1514293711-12689-137--

Barak Korren (oVirt JIRA)

tags

participants (1)