[jboss-jira] [JBoss JIRA] (SWSQE-165) Create Kiali Phase (Step 2) of Pipeline

Guilherme Baufaker Rêgo (JIRA) issues at jboss.org
Thu Apr 19 08:21:01 EDT 2018


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

Guilherme Baufaker Rêgo updated SWSQE-165:
------------------------------------------
    Description: 
{panel:title=
Step 2 (SWSQE-165)}

- Refactor [Istio and Kiali on Openshift |http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-on-Openshift/]Jenkins Job
    - Refactor prepare.env in just two steps
              *  Create a Jenkins Job  to build kiali (Make optional because I think sometimes we don't want to build Kiali - but Mandatory for PRs and Nightly Jobs) using the building part of prepare env script 
              *  Create a Jenkins Job to deploy Kiali based Mazz [Comment |https://github.com/kiali/kiali/pull/119#issuecomment-376519224] 

{code:shell}
curl https://raw.githubusercontent.com/kiali/kiali/master/deploy/openshift/kiali-configmap.yaml \
| oc create -n istio-system -f -

curl https://raw.githubusercontent.com/kiali/kiali/master/deploy/openshift/kiali.yaml \
| IMAGE_NAME=kiali/kiali IMAGE_VERSION=latest  NAMESPACE=istio-system VERBOSE_MODE=4 envsubst \
| oc create -n istio-system -f -
{code}

where IMAGE_NAME and IMAGE_VERSION could be changed to QE images (built on step 2.1.2) it can be deployed developers images by default

I don't know if the best configuration is two scripts (one for build or another to deploy) or just two functions on the same script but with optional parameters, so I'm leaving this one as you may you prefer to move this forward
{panel}


> Create Kiali Phase (Step 2) of Pipeline
> ---------------------------------------
>
>                 Key: SWSQE-165
>                 URL: https://issues.jboss.org/browse/SWSQE-165
>             Project: Kiali QE
>          Issue Type: Sub-task
>            Reporter: Guilherme Baufaker Rêgo
>
> {panel:title=
> Step 2 (SWSQE-165)}
> - Refactor [Istio and Kiali on Openshift |http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-on-Openshift/]Jenkins Job
>     - Refactor prepare.env in just two steps
>               *  Create a Jenkins Job  to build kiali (Make optional because I think sometimes we don't want to build Kiali - but Mandatory for PRs and Nightly Jobs) using the building part of prepare env script 
>               *  Create a Jenkins Job to deploy Kiali based Mazz [Comment |https://github.com/kiali/kiali/pull/119#issuecomment-376519224] 
> {code:shell}
> curl https://raw.githubusercontent.com/kiali/kiali/master/deploy/openshift/kiali-configmap.yaml \
> | oc create -n istio-system -f -
> curl https://raw.githubusercontent.com/kiali/kiali/master/deploy/openshift/kiali.yaml \
> | IMAGE_NAME=kiali/kiali IMAGE_VERSION=latest  NAMESPACE=istio-system VERBOSE_MODE=4 envsubst \
> | oc create -n istio-system -f -
> {code}
> where IMAGE_NAME and IMAGE_VERSION could be changed to QE images (built on step 2.1.2) it can be deployed developers images by default
> I don't know if the best configuration is two scripts (one for build or another to deploy) or just two functions on the same script but with optional parameters, so I'm leaving this one as you may you prefer to move this forward
> {panel}



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



More information about the jboss-jira mailing list