September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-838) Investigate how we could use git-crypt

by Prachi Yadav (Jira)

[ https://issues.jboss.org/browse/SWSQE-838?page=com.atlassian.jira.plugin.... ] Prachi Yadav commented on SWSQE-838: ------------------------------------ In jenkins we can use Secret also to encrypt the credentials ************************************* import hudson.util.Secret def secret = Secret.fromString("your password") println(secret.getEncryptedValue()) ************************************* and decrypt it ************************************* import hudson.util.Secret def secret = Secret.fromString("zlvnUMF1/hXwe3PLoitMpQ6BuQHBJ1FnpH7vmMmQ2qk=") println(secret.getPlainText()) ************************************* > Investigate how we could use git-crypt > -------------------------------------- > > Key: SWSQE-838 > URL: https://issues.jboss.org/browse/SWSQE-838 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Prachi Yadav > Priority: Minor > Labels: infrastructure > > Do we want to use git-crypt to store credentials? > Problem is how to safely share credentials among team members, how to use them in jenkins jobs and automation, etc. > # check how other teams are doing it > # suggest improvements for kiali team -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4524) In GDT, user should be able to use delete/backspace to clear cell.

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4524?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-4524: -------------------------------------- Assignee: Alexandre Bakos (was: Michael Anstis) > In GDT, user should be able to use delete/backspace to clear cell. > ------------------------------------------------------------------ > > Key: DROOLS-4524 > URL: https://issues.jboss.org/browse/DROOLS-4524 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Elizabeth Clayton > Assignee: Alexandre Bakos > Priority: Major > Labels: Field, UX, UXTeam > > Decision tables - User scenario: A user enters a value by accident and wants to clear the field to correct their error. > Currently users can't clear out the field, they should be able to Delete within a cell with backspace in GDT. In the current implementation this action is only available under right click menu, which they don't find. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4524) In GDT, user should be able to use delete/backspace to clear cell.

by Elizabeth Clayton (Jira)

Elizabeth Clayton created DROOLS-4524: ----------------------------------------- Summary: In GDT, user should be able to use delete/backspace to clear cell. Key: DROOLS-4524 URL: https://issues.jboss.org/browse/DROOLS-4524 Project: Drools Issue Type: Bug Components: Guided Decision Table Editor Reporter: Elizabeth Clayton Assignee: Michael Anstis Decision tables - User scenario: A user enters a value by accident and wants to clear the field to correct their error. Currently users can't clear out the field, they should be able to Delete within a cell with backspace in GDT. In the current implementation this action is only available under right click menu, which they don't find. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12540) Move from javax.activation:activation:1.1.1 to jakarta.activation:jakarta.activation-api:1.2.1

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12540: --------------------------------------- Summary: Move from javax.activation:activation:1.1.1 to jakarta.activation:jakarta.activation-api:1.2.1 Key: WFLY-12540 URL: https://issues.jboss.org/browse/WFLY-12540 Project: WildFly Issue Type: Sub-task Components: Server Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 18.0.0.Final Move to the Jakarta JAF project. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12496) Use correct address for node1 in integration tests

by Ivan Straka (Jira)

[ https://issues.jboss.org/browse/WFLY-12496?page=com.atlassian.jira.plugin... ] Ivan Straka updated WFLY-12496: ------------------------------- Description: Due to issues SharedStoreFailoverTestCase and ReplicatedFailoverTestCase and TransactionContextRemoteCallTestCase fails. https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-as-tes... was: Due to issues SharedStoreFailoverTestCase and ReplicatedFailoverTestCase and TransactionContextRemoteCallTestCase fails. {code:java} java.lang.AssertionError: No message was logged into the TCP syslog at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertNotNull(Assert.java:712) at org.jboss.as.test.manualmode.logging.SyslogIsNotAvailableDuringServerBootTestCase.testSyslogIsNotAvailableDuringServerBoot(SyslogIsNotAvailableDuringServerBootTestCase.java:100) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) {code} https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-as-tes... > Use correct address for node1 in integration tests > -------------------------------------------------- > > Key: WFLY-12496 > URL: https://issues.jboss.org/browse/WFLY-12496 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 18.0.0.Beta1 > Reporter: Ivan Straka > Assignee: Ivan Straka > Priority: Major > > Due to issues SharedStoreFailoverTestCase and ReplicatedFailoverTestCase and TransactionContextRemoteCallTestCase fails. > https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-as-tes... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-931) Switch to Widgetastic PF4

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-931?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-931: --------------------------------- Sprint: Kiali Sprint #28 > Switch to Widgetastic PF4 > ------------------------- > > Key: SWSQE-931 > URL: https://issues.jboss.org/browse/SWSQE-931 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > UI tests should be switched to https://github.com/RedHatQE/widgetastic.patternfly4 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-943) CVP for Service Mesh CVE Images

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-943?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-943: --------------------------------- Sprint: Kiali Sprint #28 > CVP for Service Mesh CVE Images > ------------------------------- > > Key: SWSQE-943 > URL: https://issues.jboss.org/browse/SWSQE-943 > Project: Kiali QE > Issue Type: Story > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Critical > Labels: infrastructure > > We need to have a Container Verification Pipeline testing for Service Mesh CVE Related Container Image Respins. > More info about CVP here: https://docs.engineering.redhat.com/display/CVP/Container+Verification+Pi... > Presentation done here: https://docs.google.com/presentation/d/19fs08zUOsDAYScn7DKT1vV8gEi9RTjyzk... -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-690) UI Automation - Add missing Health checks

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-690?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan closed SWSQE-690. -------------------------------- Resolution: Done > UI Automation - Add missing Health checks > ----------------------------------------- > > Key: SWSQE-690 > URL: https://issues.jboss.org/browse/SWSQE-690 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > There are a lot of TODO Health comments in UI tests. > These all should be done. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-237) Jakarta annotations missing license file in final jar distribution

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/JBEE-237?page=com.atlassian.jira.plugin.s... ] Yeray Borges resolved JBEE-237. ------------------------------- Resolution: Done > Jakarta annotations missing license file in final jar distribution > ------------------------------------------------------------------ > > Key: JBEE-237 > URL: https://issues.jboss.org/browse/JBEE-237 > Project: JBoss Enterprise Spec APIs > Issue Type: Bug > Components: jboss-annotations-api > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12387) Upgrade org.jboss.spec.javax.annotation from 1.0.1.Final to 2.0.1.Final

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-12387?page=com.atlassian.jira.plugin... ] Yeray Borges updated WFLY-12387: -------------------------------- Summary: Upgrade org.jboss.spec.javax.annotation from 1.0.1.Final to 2.0.1.Final (was: Upgrade org.jboss.spec.javax.annotation from 1.0.1.Final to 2.0.0.Final) > Upgrade org.jboss.spec.javax.annotation from 1.0.1.Final to 2.0.1.Final > ----------------------------------------------------------------------- > > Key: WFLY-12387 > URL: https://issues.jboss.org/browse/WFLY-12387 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Critical > Fix For: 18.0.0.Final > > > Upgrade Common Annotations JSR-250 to Jakarta EE > Fork: https://github.com/jboss/jboss-jakarta-annotations-api_spec > Working branch: [JBEE-207 | https://github.com/jboss/jboss-jakarta-annotations-api_spec/tree/JBEE-207] -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 2019