[jboss-jira] [JBoss JIRA] (SWSQE-113) Allocate OpenShift and Jenkins resources for testing Jaeger productized images

[Kevin Earls (JIRA)]

     [ https://issues.jboss.org/browse/SWSQE-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Earls reopened SWSQE-113:
-------------------------------


Sorry if there has been a misunderstanding here, but I still do not have the resources I need for this.  [~hhovsepy] suggested I create a job on Jenkins2 and use B15 to access the Jaeger instance that is installed with Istio.  However, my initial attempts to do this have failed.  I sent the following details out in email earlier today:

-- If I run on jenkins2 and use "agent { label 'mvn' }", what cluster does it actually run on?  (Please let me know if there is an oc command that will tell me this.) . I'm trying to run the same code I was running on B15 as part of this job http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/kearls-test/ but the tests are failing.  
-- When I run the job it says I'm using the "jenkins-slaves" project, but I don't see that on B15 or B12.  For test development and debugging I will need a project that is not torn down at the end of the job.  Is this possible.

So I either need a project on B15 which is not torn down when the node is restarted, or an agent on Jenkins2 that runs on B15 and does not remove the project when it finishes.





> Allocate OpenShift and Jenkins resources for testing Jaeger productized images
> ------------------------------------------------------------------------------
>
>                 Key: SWSQE-113
>                 URL: https://issues.jboss.org/browse/SWSQE-113
>             Project: Kiali QE
>          Issue Type: QE Task
>            Reporter: Kevin Earls
>            Assignee: Guilherme Baufaker Rêgo
>
> I need internal Jenkins and OpenShift resources for https://issues.jboss.org/browse/KIALI-336 which covers testing productized Jaeger images.  I have already started working with [~fbrychta] but we have not completely resolved this yet.  
> I can work with either of these two options
> -- A project on an OpenShift Cluster where I can create my own Jenkins instance.
> -- An external Jenkins which has an agent defined which can run on OpenShift.
> I'm not completely sure if the second solution will work, as when I run tests I will need to have access to ports that are not externally accessible.  In that case I'd be happy to use the first solution.
> Finally, this will just be for smoke and possibly simple functional tests, so I won't need high levels of resources.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)