[jboss-jira] [JBoss JIRA] (SWSQE-145) Modularize CI/CD Pipline

[Guilherme Baufaker Rêgo (JIRA)]

    [ https://issues.jboss.org/browse/SWSQE-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562676#comment-13562676 ] 

Guilherme Baufaker Rêgo edited comment on SWSQE-145 at 4/17/18 5:24 PM:
------------------------------------------------------------------------

[~mfoley] original comment:

The modularization of the CI/CD pipeline is a large topic ... epic or user story.  The first step is to do task breakdown into more discrete units of work.  

[~mmahoney] has a slide or google doc outlining, at a high-level, some thoughts  (Matt, please attach your slide to this Jira).  Using this document as input,  I would like to ask [~gbaufake] to work with [~hhovsepy]  to create a set of sub-tasks that represent the planned modularization work in some detail.   Each unit of work should be around 1 or 2 days of work, at most.    And taken together, these sub-tasks will represent the improvements.      

Once the sub-tasks are created:
* move this epic out of sprint 4
* move in the specific discrete sub-tasks that are needed for sprint #4


was (Author: gbaufake):
[~mfoley] comments:

The modularization of the CI/CD pipeline is a large topic ... epic or user story.  The first step is to do task breakdown into more discrete units of work.  

[~mmahoney] has a slide or google doc outlining, at a high-level, some thoughts  (Matt, please attach your slide to this Jira).  Using this document as input,  I would like to ask [~gbaufake] to work with [~hhovsepy]  to create a set of sub-tasks that represent the planned modularization work in some detail.   Each unit of work should be around 1 or 2 days of work, at most.    And taken together, these sub-tasks will represent the improvements.      

Once the sub-tasks are created:
* move this epic out of sprint 4
* move in the specific discrete sub-tasks that are needed for sprint #4

> Modularize CI/CD Pipline
> ------------------------
>
>                 Key: SWSQE-145
>                 URL: https://issues.jboss.org/browse/SWSQE-145
>             Project: Kiali QE
>          Issue Type: Epic
>            Reporter: Matt Mahoney
>            Assignee: Guilherme Baufaker Rêgo
>         Attachments: pipeline proposal.png
>
>
> The CI/CD pipeline has become more complex and challenging with which to build CI/CD usage-cases and to add new functionality:
> Use Case Examples:
>  1) Deploy Istio -> Deploy&build-kiali -> Deploy All Service Meshes -> Deploy Traffic Generator on all Service Meshes -> Run all test suites
>  2) Deploy built Kiali -> Run REST suite
>  3) Build and Deploy Kiali -> Run all test suites
>  4) Run UI suite on any Openshift Cluster
> Exc, etc, lots of scenarios which would be built by modules.
> Modularize into self-contained Jenkins jobs that can by themselves can do the following:
>  - Install Istio + Book Info
>  - Build Kiali
>  - Deploy Kiali
>  - Deploy Service Mesh's (all or subset there-of)
>  - Deploy Traffic Generator
>  - Run test suites + Report results to Community



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