[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:comment-tabpanel&focusedCommentId=13560648#comment-13560648 ] 

Kevin Earls commented on SWSQE-113:
-----------------------------------

Hi [~gbaufake] . I tried using the new B11 cluster this morning and ran into problems.

1.  I created a project named "jaeger-test" and tried adding a persistent Jenkins to it.  This Jenkins never finished deploying.  So I tried deleting it, and couldn't get it to delete.  Then I tried deleting the project, and as I write this it is still there in a "marked for deletion" state.

2. Then I thought I'd try the ephemeral Jenkins and see if I had any better luck.  It has exhibited the same behavior.  I've left it in place so you can look at the logs: https://b11.jonqe.lab.eng.bos.redhat.com:8443/console/project/jaeger-test2/monitoring?hideOlderResources=true&kind=All


> 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)