October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-976) Prepare downstream pipeline for UI tests

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-976?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-976. --------------------------------- Resolution: Done https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/commit/... > Prepare downstream pipeline for UI tests > ---------------------------------------- > > Key: SWSQE-976 > URL: https://issues.jboss.org/browse/SWSQE-976 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > UI tests need just one control plane and two bookinfo apps currently. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3907) [DMN Designer] Add visual indicators for imported Nodes

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3907?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-3907: ------------------------------------------- Fix Version/s: 7.29.0.Final (was: 7.28.0.Final) > [DMN Designer] Add visual indicators for imported Nodes > ------------------------------------------------------- > > Key: DROOLS-3907 > URL: https://issues.jboss.org/browse/DROOLS-3907 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, UXTeam, drools-tools > Fix For: 7.29.0.Final > > Attachments: Screen Shot 2019-04-17 at 11.55.39 AM.png, read-only-gridC2.png, read-only-gridC2.png > > > Imported models are read-only. We need to show some form of visual indicator for both Nodes (Graph View) and Boxed Expressions (Grid View). Please see the attachments for proposals for the Grid View. > Design Resolution: > * Option C: https://issues.jboss.org/secure/attachment/12449764/read-only-gridC2.png > * Keeping the hover highlight per row cell as is, because when those elements are clicked the Property panel is updated/reflects. > * Use lock icon for canvas nodes: In the components list and in the graph nodes, as illustrated in: https://issues.jboss.org/secure/attachment/12449758/Screen%20Shot%202019-... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3160) adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm)

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-3160?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-3160: ------------------------------------------- Fix Version/s: 7.29.0.Final (was: 7.28.0.Final) > adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm) > ------------------------------------------------------------ > > Key: DROOLS-3160 > URL: https://issues.jboss.org/browse/DROOLS-3160 > Project: Drools > Issue Type: Feature Request > Reporter: Michael Biarnes Kiefer > Assignee: Toni Rikkola > Priority: Major > Fix For: 7.29.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2254) Automate .proto files rebuild in pom.xml

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-2254?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-2254: ------------------------------------------- Fix Version/s: 7.29.0.Final (was: 7.28.0.Final) > Automate .proto files rebuild in pom.xml > ---------------------------------------- > > Key: DROOLS-2254 > URL: https://issues.jboss.org/browse/DROOLS-2254 > Project: Drools > Issue Type: Task > Components: tools > Affects Versions: 7.5.0.Final > Reporter: Dmitry Volodin > Assignee: Dmitry Volodin > Priority: Minor > Fix For: 7.29.0.Final > > > According to contribution guide, any .proto file or protobuf version changes it's necessary to download protoc utility and regenerate Java classes based on .proto files. > This will add automation for downloading protoc utility and Java classes generation based on Maven Protocol Buffers Plugin. There is no timestamps and other build related info inside generated Java files and no changes will be added on each new build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4551) Build fails when condition in spreadsheet contains '(' and ')' separately as a value

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4551?page=com.atlassian.jira.plugi... ] Luca Molteni resolved DROOLS-4551. ---------------------------------- Release Notes Text: See https://issues.jboss.org/browse/RHDM-1095 comments Resolution: Won't Fix > Build fails when condition in spreadsheet contains '(' and ')' separately as a value > ------------------------------------------------------------------------------------ > > Key: DROOLS-4551 > URL: https://issues.jboss.org/browse/DROOLS-4551 > Project: Drools > Issue Type: Bug > Components: build, decision tables > Affects Versions: 7.25.0.Final, 7.26.0.Final > Environment: - 7.25.0.Final or 7.26.0.Final > - spreadsheet decition table > - EscapeQuote: false > Reporter: Hiroko Miura > Assignee: Luca Molteni > Priority: Major > Labels: support > Attachments: dt-build-err.zip > > > If condition contains '(' and ')' separately as different value in value cell, build fails with error like: > {noformat} > [main] ERROR Unable to build KieBaseModel:dtables > Unable to Analyse Expression $2: > [Error: unable to resolve method using strict-mode: com.sample.Message.$2()] > [Near : {... $2 ....}] > ^ > [Line: 6, Column: 2] : [Rule name='HelloWorld_11'] > {noformat} > This worked with 7.18.0.Final-redhat-00004 (RHDM7.4.1), but fails with 7.25.0.Final or 7.26.0.Final. > Condition in DRL generated by spreadsheet compiler are different per these version. > - 7.25.0.Final/7.26.0.Final > {noformat} > m:Message(status in (Message.HELLO), errorMessage in ("Hello", "Hi"), $2) > {noformat} > - 7.24.0.Final/7.18.0.Final > {noformat} > m:Message(status in (Message.HELLO), errorMessage in ("Hello", "Hi")) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-973) Make sure that cleaning job cleans all namespaces

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-973?page=com.atlassian.jira.plugin.... ] Filip Brychta resolved SWSQE-973. --------------------------------- Resolution: Done https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl/commit/... > Make sure that cleaning job cleans all namespaces > ------------------------------------------------- > > Key: SWSQE-973 > URL: https://issues.jboss.org/browse/SWSQE-973 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Critical > Labels: infrastructure > > Problem with cleaning job is that it's called from install-maistra with parameters passed to install maistra. So in cases where the cluster contains more control planes from previous testing and one tries to reinstall it with one control plane it will only clean one leaving second there which is causing job to be stuck. > We need to clean always all namespaces for given app. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12663) Upgrade jgroups-kubernetes to 1.0.13.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12663?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12663: ---------------------------------- Description: Solves: * KUBE_PING warning with StatefulSet * KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update * Initial discovery ends up in singleton partitions was: Solves: * * KUBE_PING warning with StatefulSet * KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update * Initial discovery ends up in singleton partitions > Upgrade jgroups-kubernetes to 1.0.13.Final > ------------------------------------------ > > Key: WFLY-12663 > URL: https://issues.jboss.org/browse/WFLY-12663 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > Solves: > * KUBE_PING warning with StatefulSet > * KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > * Initial discovery ends up in singleton partitions -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12663) Upgrade jgroups-kubernetes to 1.0.13.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12663?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12663: ---------------------------------- Description: Solves: * * KUBE_PING warning with StatefulSet * KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update * Initial discovery ends up in singleton partitions > Upgrade jgroups-kubernetes to 1.0.13.Final > ------------------------------------------ > > Key: WFLY-12663 > URL: https://issues.jboss.org/browse/WFLY-12663 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > > Solves: > * * KUBE_PING warning with StatefulSet > * KUBE_PING too frequent warning metadata.labels.pod-template-hash not found in pod json. Impossible to reliably determine pod group during Rolling Update > * Initial discovery ends up in singleton partitions -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12663) Upgrade jgroups-kubernetes to 1.0.13.Final

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-12663: ------------------------------------- Summary: Upgrade jgroups-kubernetes to 1.0.13.Final Key: WFLY-12663 URL: https://issues.jboss.org/browse/WFLY-12663 Project: WildFly Issue Type: Component Upgrade Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4640) DMN Editor constraint on Type does not reflect in Decision Table

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4640?page=com.atlassian.jira.plugi... ] Michael Anstis commented on DROOLS-4640: ---------------------------------------- [~tari_manga] Could you please clarify your expectation? The {{ItemDefinition}} "Violation.Type" presumably has a constraint defined as an enumeration for "speed", "parking" and "driving under the influence". I assume you expect the {{InputClause.UnaryTests}} to auto-magically also be defined as the same enumeration? Furthermore, presumably, if the constraint for "Violation.Type" is changed the {{InputClause.UnaryTests}} should change too? Does this relationship work both ways? i.e. should the User be able to modify the {{InputClause.UnaryTests}} and this be reflected in the "Violation.Type" constraint, or should the {{InputClause.UnaryTests}} be read-only and always reflect the {{ItemDefinition}} constraint? Do you know of other scenarios when the same behaviour should apply? e.g. {{OutputClause.UnaryTests}}. Any others? > DMN Editor constraint on Type does not reflect in Decision Table > ---------------------------------------------------------------- > > Key: DROOLS-4640 > URL: https://issues.jboss.org/browse/DROOLS-4640 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Guilherme Gomes > Priority: Major > Attachments: image-2019-10-11-11-02-31-881.png > > > Editing the classic Traffic Violation item definition to put enumeration on string for the violation type "speed", "parking", ... once done in the item definition is not reflected in the decision table, and that prevents also from getting the real intended DT static analysis message for the table. > !image-2019-10-11-11-02-31-881.png|thumbnail! > in the attached screenshot I entered the data also manually in the DT's property right tab. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 October 2019