January 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26893) Create universal template and label that would accommodate different rhel needed by interop testing team

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26893?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26893: ------------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.0.AM1) > Create universal template and label that would accommodate different rhel needed by interop testing team > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26893 > URL: https://issues.redhat.com/browse/JBIDE-26893 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests, qa > Affects Versions: 4.13.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Labels: jenkins > Fix For: 4.14.0.Final > > > We would like to use universal label that would cover different rhel versions that are required by interop testing. The idea is that we will keep one/two label for interop testing slave: rhel-interop (and possibly for both stream, so rhel7-interop and rhel8-interop), which would have used image: rhel-interop-7(8)-snapshot that would have actually needed rhel version to test. During provisioning we will replace snapshot with proper rhel. This way we can keep these two labels and do not need to change interop test job label all the time via PR in cci-config repo. > Reqs: > * UMB trigger for interop rhel to run provision job with > * job will be parametrized based on rhel version given by umb message > * jenkins provisioning job build description needs to be updated to have available info about rhel version > > Pros: > * do not need to change code via PR every time there is new bits to test > * probably can be fully automated > Cons: > * only one version to test at a time > * complex and possibly unstable? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26888) Replace http access to https

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26888?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26888: ------------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.0.AM1) > Replace http access to https > ---------------------------- > > Key: JBIDE-26888 > URL: https://issues.redhat.com/browse/JBIDE-26888 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: cdi > Affects Versions: 4.13.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26878) Improve validation of CRC Binary and Pull Secret File in CRC Server Wizard and Editor

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26878?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26878: ------------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.0.AM1) > Improve validation of CRC Binary and Pull Secret File in CRC Server Wizard and Editor > ------------------------------------------------------------------------------------- > > Key: JBIDE-26878 > URL: https://issues.redhat.com/browse/JBIDE-26878 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.13.0.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Priority: Major > Fix For: 4.14.x, 4.14.0.Final > > > I can image improved validation of Pull secret file that is available in CRC Server wizard and Server Editor. > Missing validation of CRC Binary: > * Please select a valid CRC Binary, which would check that file is really a crc binary - we used similar validation for minishift where (I f I recall it right) we checked in process the output from `minishift version` or `minishift status` command. Something similar I can imagine to be used for crc. Since `crc status` could return different outputs, version seems to be better option. I would agree to postpone this validation once the crc is GA. then please ignore this and create new jira issue. Thanks! > I can imagine all of those validation in action for pull secret path input: > * Path does not exist > * Is not a file > * Is not executable (user cannot read the file) > * Is not a valid Pull secret file (probably check for if file's content is a valid json and/or we can probably validate if json's first object is "auths"? This would be nice, but simple json validation seems fine) > I believe that last three points could be validated at once by reading the file's content and creating valid json object, or else showing the error that given path is no valid a secret file. It's up implementation, right? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26858) Implement missing CDK unit tests

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26858?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26858: ------------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.0.AM1) > Implement missing CDK unit tests > -------------------------------- > > Key: JBIDE-26858 > URL: https://issues.redhat.com/browse/JBIDE-26858 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Priority: Major > Fix For: 4.14.0.Final > > > There are missing unit test that require our attention. Ie. CDKServerWizardFragment. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27012) Update maven itests to use latest stuff from Java EE 8

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27012?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27012: ------------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.0.AM1) > Update maven itests to use latest stuff from Java EE 8 > ------------------------------------------------------ > > Key: JBIDE-27012 > URL: https://issues.redhat.com/browse/JBIDE-27012 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: maven > Affects Versions: 4.14.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Major > Fix For: 4.14.0.Final > > > h2. Update maven.itests CDIConfiguratorTest testclass > - remove support for CDI 1.0 > - add support for CDI 2.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27006) Several maven.itests tests fail sporadically due to timeouts (missing wait statement or short time period)

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27006?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27006: ------------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.0.AM1) > Several maven.itests tests fail sporadically due to timeouts (missing wait statement or short time period) > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-27006 > URL: https://issues.redhat.com/browse/JBIDE-27006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.14.0.AM1 > Reporter: Zbyněk Červinka > Assignee: Zbyněk Červinka > Priority: Minor > Fix For: 4.14.0.Final > > Attachments: org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testCompilerArguments.png, org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testProcessorCustomOutput.png, org.jboss.tools.maven.ui.bot.test.configurator.CDIConfiguratorTest.testCDIConfiguratorEjbSeamInternational.png, org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator.png, org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.changeIdentifiedDependency.png > > > h2. List and description of found and fixed issues: > * *The hasNature() issue* - tests are calling the *hasNature()* method in *AbstractMavenSWTBotTest* abstract class, where a wait condition is missing. While working with the Project facets a popup window with progress bar sometimes show up. During testing it has shown up, that 10 seconds is not enought -> I am putting there 60 seconds > !org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator.png|thumbnail! > * *The createEJBProject() issue* - wait statement with too short period of time : > !org.jboss.tools.maven.ui.bot.test.configurator.CDIConfiguratorTest.testCDIConfiguratorEjbSeamInternational.png|thumbnail! > * *The createWebProject() issue* - wait statement with too short period of time : > !org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.changeIdentifiedDependency.png|thumbnail! > * *The createBasicMavenProject() issue* - wait statement with too short period of time > !org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testCompilerArguments.png|thumbnail! > * *The prepareProject() issue* - wait statement with too short period of time > !org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testProcessorCustomOutput.png|thumbnail! > * *The testAddRepositoryLinkInConversionWizard() issue* - wait statement with too short period of time > * *The convertToMavenProject() issue* - wait statement with too short period of time > * *The testMaterializeLibrary() issue* - wait statement with too short period of time > * *The createJSFProject() issue* - wait statement with too short period of time > h2. See the hasNature() issue stacktrace: > {code:java} > org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: window is available > at org.eclipse.reddeer.jface.preference.PreferenceDialog.ok(PreferenceDialog.java:119) > at org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.hasNature(AbstractMavenSWTBotTest.java:117) > at org.jboss.tools.maven.ui.bot.test.configurator.AbstractConfiguratorsTest.checkProjectWithRuntime(AbstractConfiguratorsTest.java:94) > at org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator(JSFConfiguratorTest.java:82) > {code} > h2. See the createEJBProject() issue stacktrace: > {code:java} > org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running: > Validating testEJB_CDI > at org.jboss.tools.maven.ui.bot.test.configurator.AbstractConfiguratorsTest.createEJBProject(AbstractConfiguratorsTest.java:109) > at org.jboss.tools.maven.ui.bot.test.configurator.CDIConfiguratorTest.testCDIConfiguratorEjbSeamInternational(CDIConfiguratorTest.java:123) > {code} > h2. See the createWebProject() issue stacktrace: > {code:java} > org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running: > loading https://maven.apache.org/xsd/maven-4.0.0.xsd > org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.createWebProject(AbstractMavenSWTBotTest.java:280) > at org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.createWithRuntime(MavenConversionTest.java:204) > at org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.changeIdentifiedDependency(MavenConversionTest.java:123) > {code} > h2. See the createBasicMavenProject() issue stackstrace: > {code:java} > org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: The following jobs are still running: > Validating test > at org.eclipse.reddeer.eclipse.core.resources.AbstractResource.open(AbstractResource.java:78) > at org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.openPom(AbstractMavenSWTBotTest.java:331) > at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.setCompilerArguments(APTPropertiesPageTest.java:298) > at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testCompilerArguments(APTPropertiesPageTest.java:128) > {code} > h2. See the prepareProject() issue stackstrace: > {code:java} > org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: The following jobs are still running: > Validating test > at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.prepareProject(APTPropertiesPageTest.java:410) > at org.jboss.tools.maven.ui.bot.test.apt.APTPropertiesPageTest.testProcessorCustomOutput(APTPropertiesPageTest.java:192) > {code} > h2. See the testAddRepositoryLinkInConversionWizard() issue stackstrace: > {code:java} > org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running: > Validating WebProject > at org.jboss.tools.maven.ui.bot.test.conversion.MavenConversionTest.testAddRepositoryLinkInConversionWizard(MavenConversionTest.java:172) > {code} > h2. See the convertToMavenProject() issue stackstrace: > {code:java} > at org.eclipse.reddeer.common.wait.WaitWhile.throwWaitTimeOutException(WaitWhile.java:116) > at org.jboss.tools.maven.ui.bot.test.AbstractMavenSWTBotTest.convertToMavenProject(AbstractMavenSWTBotTest.java:241) > at org.jboss.tools.maven.ui.bot.test.configurator.JSFConfiguratorTest.testJSFConfigurator(JSFConfiguratorTest.java:81) > {code} > h2. See the testMaterializeLibrary() issue stackstrace: > {code:java} > org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 60 s.: The following jobs are still running: > Validating example > at org.jboss.tools.maven.ui.bot.test.conversion.MaterializeLibraryTest.testMaterializeLibrary(MaterializeLibraryTest.java:86) > {code} > h2. See the createJSFProject() issue stackstrace: > {code:java} > org.eclipse.reddeer.common.exception.WaitTimeoutExpiredException: > Timeout after: 60 s.: The following jobs are still running: > Launching JSFProject7_1.2 > Validating JSFProject7_1.2 > at org.jboss.tools.maven.ui.bot.test.project.JSFProjectTest.createJSFProject(JSFProjectTest.java:72) > at org.jboss.tools.maven.ui.bot.test.project.JSFProjectTest.createJSFProjectTest_AS7_JSFv2(JSFProjectTest.java:46) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27000) Ensure we use the latest version of minishift.yaml

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-27000?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-27000: ------------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.0.AM1) > Ensure we use the latest version of minishift.yaml > -------------------------------------------------- > > Key: JBIDE-27000 > URL: https://issues.redhat.com/browse/JBIDE-27000 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.13.0.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > > The server plugin embeds a minishift.yaml file. We should ensure the latest version is embedded. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26995) Cont'd: Documenting QE - CI BP in use for CR Studio QE /Adapters

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26995?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26995: ------------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.0.AM1) > Cont'd: Documenting QE - CI BP in use for CR Studio QE /Adapters > ---------------------------------------------------------------- > > Key: JBIDE-26995 > URL: https://issues.redhat.com/browse/JBIDE-26995 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.14.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.14.0.Final > > > Cont'd of JBIDE-26788. Adding example adding new job, applying best practices, using templates and shared libraries. Usage of UMB triggering in pipelines. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26994) Provide an odo based developer experience

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26994?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26994: ------------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.0.AM1) > Provide an odo based developer experience > ----------------------------------------- > > Key: JBIDE-26994 > URL: https://issues.redhat.com/browse/JBIDE-26994 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.14.0.AM1 > Reporter: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26989) pre select default extensions

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26989?page=com.atlassian.jira.plug... ] Stephane Bouchet updated JBIDE-26989: ------------------------------------- Fix Version/s: 4.14.0.Final (was: 4.14.0.AM1) > pre select default extensions > ----------------------------- > > Key: JBIDE-26989 > URL: https://issues.redhat.com/browse/JBIDE-26989 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: quarkus > Affects Versions: 4.14.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > > The extensions model has the notion of default extensions. Such extensions should be pre selected when launching the wizard -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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

jbosstools-issues January 2020