April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-665) Test case coverage for Istio

by Yuanlin Xu (Jira)

[ https://issues.jboss.org/browse/SWSQE-665?page=com.atlassian.jira.plugin.... ] Yuanlin Xu resolved SWSQE-665. ------------------------------ Resolution: Done We don't have missing fields when we are testing Istio now. This task is done. > Test case coverage for Istio > ---------------------------- > > Key: SWSQE-665 > URL: https://issues.jboss.org/browse/SWSQE-665 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Yuanlin Xu > Priority: Major > Labels: pqi > > Some areas are missing which we are not testing for Istio. Need to focus on that. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-668) Checklist for custom fields in order to support existing and future workflows for Istio

by Yuanlin Xu (Jira)

[ https://issues.jboss.org/browse/SWSQE-668?page=com.atlassian.jira.plugin.... ] Yuanlin Xu commented on SWSQE-668: ---------------------------------- We don't see QE Test Coverage, SFDC Cases Counter , SFDC Cases Links fields in MaistraIstio Polarion project. It looks like they are general Polarion fields and we don't have access to search them. > Checklist for custom fields in order to support existing and future workflows for Istio > --------------------------------------------------------------------------------------- > > Key: SWSQE-668 > URL: https://issues.jboss.org/browse/SWSQE-668 > Project: Kiali QE > Issue Type: QE Task > Reporter: Prachi Yadav > Assignee: Yuanlin Xu > Priority: Major > Labels: pqi > > project MUST have the following custom fields in order to support existing and future workflows and visualizations: > QE Test Coverage with values +, -, and ? (Null is supported) > SFDC Cases Counter > SFDC Cases Links > These custom fields must exist as above so that we do not need to customize logic for any one-offs. The SFDC Cases * fields are there to support "integration" with our SalesForce system used by CEE/GSS for customer cases and the links here are links to SFDC customer cases. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-654) Istio-Investigate and work on automated/not automated/only manual type of test cases and mark them in polarion

by Yuanlin Xu (Jira)

[ https://issues.jboss.org/browse/SWSQE-654?page=com.atlassian.jira.plugin.... ] Yuanlin Xu resolved SWSQE-654. ------------------------------ Resolution: Done All Istio test cases have marked automated or not automated in Polarion. This task is done. > Istio-Investigate and work on automated/not automated/only manual type of test cases and mark them in polarion > -------------------------------------------------------------------------------------------------------------- > > Key: SWSQE-654 > URL: https://issues.jboss.org/browse/SWSQE-654 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Assignee: Yuanlin Xu > Priority: Major > Labels: pqi > > Istio-Investigate and work on automated/not automated/only manual type of test cases and mark them in polarion -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-712) Ability to create 2nd bookinfo via operator

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-712?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-712: ---------------------------------- Sprint: Kiali Sprint #22 (was: Kiali Sprint #21) > Ability to create 2nd bookinfo via operator > ------------------------------------------- > > Key: SWSQE-712 > URL: https://issues.jboss.org/browse/SWSQE-712 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Priority: Major > Labels: infrastructure > > Currently our https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/job/bookinfo-operator/ > jenkins job allows to create only one bookinfo namespace. > But UI Automation framework requires bookinfo2 namespace for parallel running. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-640) Kiali Pipeline 3.0

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-640?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-640: ---------------------------------- Sprint: Kiali Sprint #22 (was: Kiali Sprint #21) > Kiali Pipeline 3.0 > ------------------ > > Key: SWSQE-640 > URL: https://issues.jboss.org/browse/SWSQE-640 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Critical > Labels: infrastructure > > Since we are moving from Ansible Upstream installer ( it will be deprecated on Istio 1.1 (https://github.com/istio/istio/issues/12262), Bookinfo has been updated on Kiali Test Mesh Operator (KIALI-2520 and SWSQE-594) and we are moving to central-ci Jenkins, move to DSL jobs, I think it is a good opportunity to make a better pipeline with small number of jobs (currently we have lot of jobs which are not technically accurate anymore) > At least these jobs need to change: > - Nightly Jobs > - Complex Mesh > - Kiali Test Meshes > - Clean Istio Resources > - Istio Upstream > - Kiali on Openshift > - Istio and Kiali on Openshift > - Maistra Job (it might need to change because the new operator based on golang) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-699) Code coverage for kiali

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-699?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-699: ---------------------------------- Sprint: Kiali Sprint #22 (was: Kiali Sprint #21) > Code coverage for kiali > ----------------------- > > Key: SWSQE-699 > URL: https://issues.jboss.org/browse/SWSQE-699 > Project: Kiali QE > Issue Type: Story > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > It would be nice to have code coverage report for kiali. We can generate report for all existing test suites. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-709) Push Kiali-QE Builds To Quay.io

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-709?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-709: ---------------------------------- Sprint: Kiali Sprint #22 (was: Kiali Sprint #21) > Push Kiali-QE Builds To Quay.io > ------------------------------- > > Key: SWSQE-709 > URL: https://issues.jboss.org/browse/SWSQE-709 > Project: Kiali QE > Issue Type: Task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > Push kialiqe builds to Quay.io, and not Dockerhub. > Perhaps there is an alternative internal Repo. If not Quay.io seems to be the direction the team is headed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-704) Review jenkins2 settings

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-704?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-704: ---------------------------------- Sprint: Kiali Sprint #22 (was: Kiali Sprint #21) > Review jenkins2 settings > ------------------------ > > Key: SWSQE-704 > URL: https://issues.jboss.org/browse/SWSQE-704 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > Check https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/configure for kubernetes settings and usage of b21.jonqe.lab.eng.bos.redhat.com which is now part of prod cluster. > Also update https://mojo.redhat.com/docs/DOC-1168333 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-560) OCP 4.0 on Openstack

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-560?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-560: ---------------------------------- Sprint: Kiali Sprint #22 (was: Kiali Sprint #21) > OCP 4.0 on Openstack > -------------------- > > Key: SWSQE-560 > URL: https://issues.jboss.org/browse/SWSQE-560 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > New Openshift Installer supports OpenStack (https://github.com/openshift/installer/blob/master/docs/user/openstack/RE...) > It can be a substitute for OSOOS. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-626) Investigate options to share docker registry with istio team

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-626?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-626: ---------------------------------- Sprint: Kiali Sprint #22 (was: Kiali Sprint #21) > Investigate options to share docker registry with istio team > ------------------------------------------------------------ > > Key: SWSQE-626 > URL: https://issues.jboss.org/browse/SWSQE-626 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > Tiago runs his docker registry in Central CI > We run our registry in b22 ocp cluster. > Do we want to run just one registry? > What would be content: > * product images > * jenkins slaves images > * ?? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019