]
Filip Brychta resolved SWSQE-202.
---------------------------------
Resolution: Done
It's now possible to use mvn && b15 labels in your jenkins job configuration
to start jenkins mvn slave on b15. This configuration should survive re-install of OS
cluster on b15 which is done as part of
Complete Cloud definition for
b15.jonqe.lab.eng.bos.redhat.com on
Jenkins2
--------------------------------------------------------------------------
Key: SWSQE-202
URL:
https://issues.jboss.org/browse/SWSQE-202
Project: Kiali QE
Issue Type: QE Task
Reporter: Kevin Earls
Assignee: Filip Brychta
Priority: Blocker
In order to be able to complete
https://issues.jboss.org/browse/KIALI-336 I need to be
able to launch tests on B15 from Jenkins2. I have created a new entry named
b15.jonqe.lab.eng.bos.redhat.com under Manage Jenkins -> Configure System but was not
able to get it to connect. The following items are still required
1. This entry needs to be configured so it can connect in the same way that the B21 entry
does. The "Kubernetes server certificate key" needs to be added, as well as
proper credentials.
2. A kubernetes pod template needs to be added, similar to the jenkins-slave-maven entry
that exists for B21. Names should be updated so it is clear which cluster these are
running on.
3. A "jaeger-test" project should be created on B15, and it should be recreated
whenever that cluster is recreated.