September 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-419) Enhance Maistra Pipeline Support

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-419?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-419: ------------------------------------------ Description: Maistra Pipeline would need to have some additions to have better support (Some of them include) - Remove Maistra Job from Upstream Pipeline (SWSQE-423) - Add Minimal CR option (this will install default versions listed on istio-operator) - Separate OPENSHIFT_ISTIO_VERSION variable - one for istio operator version and other for istio openshift ansible - Include Option to run or not run Kiali Istio Checker - Include Bookinfo - Include E2E Test Run - Include UI Test Run was: Maistra Pipeline would need to have some additions to have better support (Some of them include) - Remove Maistra Job from Upstream Pipeline (SWSQE-419) - Add Minimal CR option (this will install default versions listed on istio-operator) - Separate OPENSHIFT_ISTIO_VERSION variable - one for istio operator version and other for istio openshift ansible - Include Option to run or not run Kiali Istio Checker - Include Bookinfo - Include E2E Test Run - Include UI Test Run Team: Infrastructure (was: Infrastructure) > Enhance Maistra Pipeline Support > -------------------------------- > > Key: SWSQE-419 > URL: https://issues.jboss.org/browse/SWSQE-419 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Maistra Pipeline would need to have some additions to have better support (Some of them include) > - Remove Maistra Job from Upstream Pipeline (SWSQE-423) > - Add Minimal CR option (this will install default versions listed on istio-operator) > - Separate OPENSHIFT_ISTIO_VERSION variable - one for istio operator version and other for istio openshift ansible > - Include Option to run or not run Kiali Istio Checker > - Include Bookinfo > - Include E2E Test Run > - Include UI Test Run -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-423) Remove Maistra Job from Upstream Pipeline

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-423?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-423. ------------------------------------------- Resolution: Done > Remove Maistra Job from Upstream Pipeline > ----------------------------------------- > > Key: SWSQE-423 > URL: https://issues.jboss.org/browse/SWSQE-423 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > - Installing Maistra, deleting and then installing Istio Upstream might lead to problems. (Istio Upstream job doesn't delete istio-operator namespace and maistra resources) > - Separating the pipelines seems to be an option, since operators numbers will increase -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-426) Automate Kiali Client Process

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-426: --------------------------------------------- Summary: Automate Kiali Client Process Key: SWSQE-426 URL: https://issues.jboss.org/browse/SWSQE-426 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Michael Foley - Kiali Client was released manually so far by [~gbaufake]. We need an automated way to do it -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-426) Automate Kiali Client Process

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-426?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo reassigned SWSQE-426: --------------------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Michael Foley) > Automate Kiali Client Process > ----------------------------- > > Key: SWSQE-426 > URL: https://issues.jboss.org/browse/SWSQE-426 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > - Kiali Client was released manually so far by [~gbaufake]. We need an automated way to do it -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-425) Release Kiali Client 0.4.8

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-425?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-425. ------------------------------------------- Resolution: Done - Kiali Python Client 0.4.8 was released (https://pypi.org/project/kiali-client/0.4.8/) > Release Kiali Client 0.4.8 > -------------------------- > > Key: SWSQE-425 > URL: https://issues.jboss.org/browse/SWSQE-425 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > - Kiali Client Needs to be released to 0.4.8 to support https://github.com/kiali/kiali-client-python/pull/11 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-425) Release Kiali Client 0.4.8

by Guilherme Baufaker Rêgo (JIRA)

Guilherme Baufaker Rêgo created SWSQE-425: --------------------------------------------- Summary: Release Kiali Client 0.4.8 Key: SWSQE-425 URL: https://issues.jboss.org/browse/SWSQE-425 Project: Kiali QE Issue Type: Sub-task Reporter: Guilherme Baufaker Rêgo Assignee: Guilherme Baufaker Rêgo - Kiali Client Needs to be released to 0.4.8 to support https://github.com/kiali/kiali-client-python/pull/11 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-399) Enhance Kiali Python Client

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-399?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-399: ------------------------------------------ Labels: kiali-python-client (was: ) Team: Infrastructure (was: Infrastructure) > Enhance Kiali Python Client > --------------------------- > > Key: SWSQE-399 > URL: https://issues.jboss.org/browse/SWSQE-399 > Project: Kiali QE > Issue Type: Story > Reporter: Guilherme Baufaker Rêgo > Assignee: Sunil kondkar > Labels: kiali-python-client > > Kiali Python Client is critical part of our testing code. > I need help with documentation, verifying if the methods are correct, updating the new ones, creating tests to evaluate change on the routes (https://github.com/kiali/kiali/blob/master/routing/routes.go) > API Documentation - https://www.kiali.io/api/paths/ > Kiali API enpoints -> https://github.com/kiali/kiali-client-python/blob/master/kiali/api.py -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2953) [DMN Designer] [IE11] Custom data type inline menu can not be hidden

by Daniel José dos Santos (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2953?page=com.atlassian.jira.plugi... ] Daniel José dos Santos reassigned DROOLS-2953: ---------------------------------------------- Assignee: Daniel José dos Santos (was: Guilherme Carreiro) > [DMN Designer] [IE11] Custom data type inline menu can not be hidden > -------------------------------------------------------------------- > > Key: DROOLS-2953 > URL: https://issues.jboss.org/browse/DROOLS-2953 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.11.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Minor > Labels: drools-tools > Attachments: Port Clearance Rules - Solution 3.dmn, Screenshot from 2018-09-03 12-18-31.png > > > If user invokes inline menu in the custom data type dialog and decide to hide it without any action performed, he is unable to do it. The menu remains shown partially. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2788: -------------------------------- Attachment: now-headers.png > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-2788 > URL: https://issues.jboss.org/browse/DROOLS-2788 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png > > > As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2788) UX to support selection of multiple data/domain object instances

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2788?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2788: ------------------------------------- [~danielezonca] [~tirelli] Now every DO regardless of whether it has "children" (see tree above) is in the same row with non "nested" elements. If we introduce headers for instances, then will every nested DO have headers. I made a pic to illustrate my question: !now-headers.png|thumbnail! > UX to support selection of multiple data/domain object instances > ---------------------------------------------------------------- > > Key: DROOLS-2788 > URL: https://issues.jboss.org/browse/DROOLS-2788 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-24 at 2.22.20 PM.png, Screen Shot 2018-09-18 at 1.35.43 PM.png, Screen Shot 2018-09-19 at 11.44.07 AM.png, now-headers.png > > > As a user I want to define multiple data/domain object instances per scenario (i.e. possible to have a scenario with more than one instance of “Person”), so that I can create a test scenario. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 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 September 2018