December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-912) Improve clean evn job to always clean all controll planes

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-912?page=com.atlassian.jira.plugin... ] Filip Brychta resolved SWSQE-912. --------------------------------- Resolution: Done > Improve clean evn job to always clean all controll planes > --------------------------------------------------------- > > Key: SWSQE-912 > URL: https://issues.redhat.com/browse/SWSQE-912 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > When we have cluster with more control planes and then we start upstream pipeline with just one control plane the clean env job is stuck on deleting operator. We need to clean everything before installing new control plane. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-837) cee gitlab will be merged

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-837?page=com.atlassian.jira.plugin... ] Filip Brychta closed SWSQE-837. ------------------------------- Resolution: Done All is working fine after the merge > cee gitlab will be merged > ------------------------- > > Key: SWSQE-837 > URL: https://issues.redhat.com/browse/SWSQE-837 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We have repos in cee github which will be merged. > Details here - https://projects.engineering.redhat.com/browse/PNTSYSOPS-5968 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-753) OCP token for production cluster expires after ~ 2 weeks

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-753?page=com.atlassian.jira.plugin... ] Filip Brychta closed SWSQE-753. ------------------------------- Resolution: Done This was resolved probably by some jenkins update > OCP token for production cluster expires after ~ 2 weeks > -------------------------------------------------------- > > Key: SWSQE-753 > URL: https://issues.redhat.com/browse/SWSQE-753 > Project: Kiali QE > Issue Type: Bug > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > > Jenkins master is using token for ocp production cluster which expires after ~2 days and is not re-created correctly so it's not possible to create new jenkins slaves. Restart of jenkins master re-generates the token so it's the simplest workaround right now. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

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

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-626?page=com.atlassian.jira.plugin... ] Filip Brychta closed SWSQE-626. ------------------------------- Resolution: Out of Date Product images are stored in quey, jenkins slaves in b22, and there is also a possibility to use internal registry in PSI OCP clusters. > Investigate options to share docker registry with istio team > ------------------------------------------------------------ > > Key: SWSQE-626 > URL: https://issues.redhat.com/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.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4872) "customSerializationMapper" in JSONMarshaller.configureMarshaller() doesn't respect JSONMarshallerExtensions

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4872?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4872: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9)) > "customSerializationMapper" in JSONMarshaller.configureMarshaller() doesn't respect JSONMarshallerExtensions > ------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-4872 > URL: https://issues.redhat.com/browse/DROOLS-4872 > Project: Drools > Issue Type: Component Upgrade > Components: kie server > Affects Versions: 7.29.0.Final, 7.30.0.Final, 7.31.0.Final > Reporter: Petar Tahchiev > Assignee: Toshiya Kobayashi > Priority: Major > > Hello, > as discussed here: > https://groups.google.com/forum/#!topic/drools-setup/85k05vo0Ix8 > I'm trying to configure the JSONMarshaller so I can serialize/deserialize objects of type {{javax.money.MonetaryAmount}}, however even though I register my own {{JSONMarshallerExtension}} seems like the conversion is handled by the {{customSerializationMapper}} in {{JSONMarshaller.configureMarshaller()}} and this mapper is not passed to the extension so there's no way I can configure it. This leads to the attributes of type {{MonetaryAmount}} being serialized in a wrong way (not using any modules registered through the {{JSONMarshallerExtension}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4875) DMN validation message alignment to DMN XSD constraint

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4875?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4875: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9)) > DMN validation message alignment to DMN XSD constraint > ------------------------------------------------------ > > Key: DROOLS-4875 > URL: https://issues.redhat.com/browse/DROOLS-4875 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4876) GDST: Aliases only work for Strings

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4876?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4876: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9)) > GDST: Aliases only work for Strings > ----------------------------------- > > Key: DROOLS-4876 > URL: https://issues.redhat.com/browse/DROOLS-4876 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > If you use the Column creator and add an alias for any other column type than String, the aliases do not show up. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4889) DMN wrong operator dmn compilation test

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4889?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4889: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9)) > DMN wrong operator dmn compilation test > --------------------------------------- > > Key: DROOLS-4889 > URL: https://issues.redhat.com/browse/DROOLS-4889 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4807) [DMN Designer] Do not group V&V messages by UUID

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4807?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4807: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9)) > [DMN Designer] Do not group V&V messages by UUID > ------------------------------------------------ > > Key: DROOLS-4807 > URL: https://issues.redhat.com/browse/DROOLS-4807 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.30.0.Final > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: V&V.png, dmn1.dmn > > > The V&V results are grouped by UUID. See attached screen-shot. > These items are reported individually by {{kie-dmn-validation}} but grouped by {{org.kie.workbench.common.dmn.showcase.backend.validation.ValidationServiceImpl}} in the _standalone_ webapp however I fear Stunner's generic {{ValidationService}} does the same in Business Central and hence reporting DMN V&V per-line may be more troublesum. > See [here|https://github.com/kiegroup/kie-wb-common/blob/master/kie-wb-common-...] that should more correctly be:- > {code} > @Override > public Collection<DiagramElementViolation<RuleViolation>> validate(Diagram diagram) { > return domainViolations(diagram).stream() > .filter(v -> Objects.nonNull(v.getUUID())) > .filter(v -> !"null".equals(v.getUUID())) > .map(v -> new ElementViolationImpl.Builder().setUuid(v.getUUID()).setDomainViolations(Collections.singletonList(v)).build()) > .collect(Collectors.toList()); > } > {code} > h3. Acceptance criteria > - Create a DMN file > - Add a Decision node with no content > - Validate it > - Each validation message should be a separate item in the Alert panel -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4846) [DMN Designer] User is unable to save model when multilevel structure is removed

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4846?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4846: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9)) > [DMN Designer] User is unable to save model when multilevel structure is removed > -------------------------------------------------------------------------------- > > Key: DROOLS-4846 > URL: https://issues.redhat.com/browse/DROOLS-4846 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Minor > Labels: drools-tools > Attachments: multilevel-structure.webm > > > There is scenario causing user is not able to save the DMN file anymore. If is editing some multilevel structure field, but he decides in the middle of editing to remove whole top level structure, the save button of the designer remains disabled. See the attached video. > We should either fix this scenario or drop the *disable save button* feature. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2019