March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-655) Kiali tableue reports-Test execution report does not show all the sprints

by Sunil Kondkar (Jira)

Sunil Kondkar created SWSQE-655: ----------------------------------- Summary: Kiali tableue reports-Test execution report does not show all the sprints Key: SWSQE-655 URL: https://issues.jboss.org/browse/SWSQE-655 Project: Kiali QE Issue Type: QE Task Reporter: Sunil Kondkar Kiali tableue reports-Test execution report does not show all the sprints To-do: -Search if the sprint milestones exist, if not then create -Link existing test plans of each sprint to related milestone sprint -Verify if reports show all test cases and sprints -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4389) deploy fails in batch when operation is validated

by Jean-Francois Denise (Jira)

Jean-Francois Denise created WFCORE-4389: -------------------------------------------- Summary: deploy fails in batch when operation is validated Key: WFCORE-4389 URL: https://issues.jboss.org/browse/WFCORE-4389 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise - The DMR of the deploy command although accepted by the server is not compliant with operation description. In batch mode the operations are validated, the following content is not valid: - /deployments=foo:add(name=foo, ...). name is not a valid argument - :full-replace-deployment is sent without an empty address. The workaround is to disable the operation-validation check. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

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

by Sunil Kondkar (Jira)

Sunil Kondkar created SWSQE-654: ----------------------------------- Summary: Kiali-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 Kiali-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)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-653) Kiali tableue reports-Investigate and work on test cases monthly trend - percenatge of automated test cases going down

by Sunil Kondkar (Jira)

Sunil Kondkar created SWSQE-653: ----------------------------------- Summary: Kiali tableue reports-Investigate and work on test cases monthly trend - percenatge of automated test cases going down Key: SWSQE-653 URL: https://issues.jboss.org/browse/SWSQE-653 Project: Kiali QE Issue Type: QE Task Reporter: Sunil Kondkar Kiali tableue reports on test cases monthly trend shows percenatge of automated test cases going down -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-586) Switch kiali-qe-utils repository into GitLab

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-586?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-586: ----------------------------------- Assignee: Filip Brychta > Switch kiali-qe-utils repository into GitLab > -------------------------------------------- > > Key: SWSQE-586 > URL: https://issues.jboss.org/browse/SWSQE-586 > Project: Kiali QE > Issue Type: QE Task > Reporter: Jeeva Kandasamy > Assignee: Filip Brychta > Priority: Optional > Labels: infrastructure > > Looks like internal GitLab[1] is ready to use. > We can move our kiali-qe-utils[2] to GitLab > Why? > * GitLab looks cool > * Friendly web code browser > * Review PR's > * integrate with CI (if needed) > * improves collaboration > We should get others feedback in our team on this task. > [1] - https://gitlab.cee.redhat.com > [2] - http://git.host.prod.eng.bos.redhat.com/git/kiali-qe-utils.git/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-603) Migrate Jenkins2 CI Pipeline to Central CI

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-603?page=com.atlassian.jira.plugin.... ] Matthew Mahoney updated SWSQE-603: ---------------------------------- Sprint: (was: Kiali Sprint #20) > Migrate Jenkins2 CI Pipeline to Central CI > ------------------------------------------- > > Key: SWSQE-603 > URL: https://issues.jboss.org/browse/SWSQE-603 > Project: Kiali QE > Issue Type: Story > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > QE CI/CP Integration -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-603) Migrate Jenkins2 CI Pipeline to Central CI

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-603?page=com.atlassian.jira.plugin.... ] Matthew Mahoney commented on SWSQE-603: --------------------------------------- Note: Team reviewed the Pros/Cons doc: Decision was to stay on our current team managed Jenkins instance, for the time being. Will evaluate moving to Openshift Jenkins ** Moving to Backlog > Migrate Jenkins2 CI Pipeline to Central CI > ------------------------------------------- > > Key: SWSQE-603 > URL: https://issues.jboss.org/browse/SWSQE-603 > Project: Kiali QE > Issue Type: Story > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > QE CI/CP Integration -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-613) Document Manual Events

by Matthew Mahoney (Jira)

[ https://issues.jboss.org/browse/SWSQE-613?page=com.atlassian.jira.plugin.... ] Matthew Mahoney resolved SWSQE-613. ----------------------------------- Resolution: Done > Document Manual Events > ---------------------- > > Key: SWSQE-613 > URL: https://issues.jboss.org/browse/SWSQE-613 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matthew Mahoney > Assignee: Matthew Mahoney > Priority: Major > Labels: infrastructure > > Document what can not be automated > Document why it can not be automated -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-625) Get access for kiali qe to https://gitlab.cee.redhat.com/istio

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-625?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-625. --------------------------------- Resolution: Done > Get access for kiali qe to https://gitlab.cee.redhat.com/istio > -------------------------------------------------------------- > > Key: SWSQE-625 > URL: https://issues.jboss.org/browse/SWSQE-625 > Project: Kiali QE > Issue Type: Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We agreed that we want to share one organization among istio and kiali in cee gitlab. > Note that there is already https://gitlab.cee.redhat.com/kiali-qe/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11911) Remove READ_TIMEOUT from cannel configuration options

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFLY-11911?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil moved WFCORE-4365 to WFLY-11911: ------------------------------------------------- Project: WildFly (was: WildFly Core) Key: WFLY-11911 (was: WFCORE-4365) Component/s: EJB (was: Management) Affects Version/s: 16.0.0.Final (was: 8.0.0.Final) > Remove READ_TIMEOUT from cannel configuration options > ----------------------------------------------------- > > Key: WFLY-11911 > URL: https://issues.jboss.org/browse/WFLY-11911 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 16.0.0.Final > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Major > > The only configuration options allowed on the channel are > RemotingOptions.TRANSMIT_WINDOW_SIZE, > RemotingOptions.MAX_OUTBOUND_MESSAGES > RemotingOptions.RECEIVE_WINDOW_SIZE > RemotingOptions.MAX_INBOUND_MESSAGES > RemotingOptions.MAX_OUTBOUND_MESSAGE_SIZE > RemotingOptions.MAX_INBOUND_MESSAGE_SIZE. > Standalone.xml/domain.xml file show READ_TIMEOUT as an example option and should be removed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2019