November 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-25444) Declare JAVAxx ENV vars on mac slaves

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25444?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25444: ------------------------------- Description: JAVA19 env vars need to be declared on OSX boxes, as they were for windows and rhel CCI slaves (via JBIDE-25285). was: JAVA19 env vars need to be declared: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > Declare JAVAxx ENV vars on mac slaves > ------------------------------------- > > Key: JBIDE-25444 > URL: https://issues.jboss.org/browse/JBIDE-25444 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.5.1.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.2.AM2 > > > JAVA19 env vars need to be declared on OSX boxes, as they were for windows and rhel CCI slaves (via JBIDE-25285). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25444) Declare "JAVA19" ENV vars on mac slaves

by Martin Malina (JIRA)

Martin Malina created JBIDE-25444: ------------------------------------- Summary: Declare "JAVA19" ENV vars on mac slaves Key: JBIDE-25444 URL: https://issues.jboss.org/browse/JBIDE-25444 Project: Tools (JBoss Tools) Issue Type: Task Components: build, qa Affects Versions: 4.5.1.Final Reporter: Pavol Srna Assignee: Pavol Srna Fix For: 4.5.2.AM2 JAVA19 env vars need to be declared: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25444) Declare JAVAxx ENV vars on mac slaves

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25444?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-25444: ---------------------------------- Summary: Declare JAVAxx ENV vars on mac slaves (was: Declare "JAVA19" ENV vars on mac slaves) > Declare JAVAxx ENV vars on mac slaves > ------------------------------------- > > Key: JBIDE-25444 > URL: https://issues.jboss.org/browse/JBIDE-25444 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, qa > Affects Versions: 4.5.1.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.2.AM2 > > > JAVA19 env vars need to be declared: > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... > https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/b... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25303: ------------------------------------------ [~aurelien.pupier] Like I pointed out in https://issues.jboss.org/browse/OSFUSE-548?focusedCommentId=13495272&page... I cannot make the hot-code replace to happen. Any ideas? > Server adapter: support hot-deployment on OpenShift for SpringBoot app > ---------------------------------------------------------------------- > > Key: JBIDE-25303 > URL: https://issues.jboss.org/browse/JBIDE-25303 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.1.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.2.AM2 > > Attachments: fuse-on-openshift.zip, spring-boot-demo.zip > > > currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file. > The requirements are: > - rsync unpacked jar > - rsync without the jar name as folder > - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated) > use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools": > - there is a SpringBoot app deployed on OpenShift > - the developer want to develop evolution of the SpringBoot app > -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance > -- Remote java debug should be available when the OpenShift server adapter is in debug mode. > Steps: > # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot) > # EXEC: Import project within fuse-on-openshift.zip into your workspace > # EXEC: open launch configuration and change: > ** -Dkubernetes.master= so that it first your cdk instance > ** -Dkubernetes.namespace= to the name of the project that you create in step 1. > # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk) > # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running. > # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service) > # ASSERT: server adapter is created and is *[started]* > # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service) > # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end > {code} > simple-route - >>> 455 > simple-route - >>> 695 > simple-route - >>> 935 > {code} > # EXEC: In Project Explorer: open class MyTransformer and change the transform method > # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25443) CDK itests fail on MAC os slaves with mysterious system warning dialog

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25443?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25443: --------------------------------------- That seems reasonable! I logged in the machine, closed the dialog and run the tests again, so let's see whether it was as you said... > CDK itests fail on MAC os slaves with mysterious system warning dialog > ---------------------------------------------------------------------- > > Key: JBIDE-25443 > URL: https://issues.jboss.org/browse/JBIDE-25443 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, qa > Affects Versions: 4.5.2.AM2 > Environment: MacOS > Reporter: Ondrej Dockal > Assignee: Martin Malina > Priority: Critical > Attachments: image-2017-11-29-12-52-27-497.png > > > CDK itests are sometimes blocked by system dialog (saying: JBoss Tools Test Applicaiton quit unexpectedly) and causes failures in tests. Also could be just just consequence of crashed test app... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25443) CDK itests fail on MAC os slaves with mysterious system warning dialog

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25443?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-25443: --------------------------------------- To make it clear, it seems that there was just one crash on bigmek in recent days and the dialog just stayed there which is normal. So hopefully it won't be happening again. > CDK itests fail on MAC os slaves with mysterious system warning dialog > ---------------------------------------------------------------------- > > Key: JBIDE-25443 > URL: https://issues.jboss.org/browse/JBIDE-25443 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, qa > Affects Versions: 4.5.2.AM2 > Environment: MacOS > Reporter: Ondrej Dockal > Assignee: Martin Malina > Priority: Critical > Attachments: image-2017-11-29-12-52-27-497.png > > > CDK itests are sometimes blocked by system dialog (saying: JBoss Tools Test Applicaiton quit unexpectedly) and causes failures in tests. Also could be just just consequence of crashed test app... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25438: ---------------------------------- Description: Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. * repair discovery itests * finish adding of mocking cdk binaries in unsupported cdk versions * update suites to run faster test classes * remove deprecated test cases * think of skipping registration and adding one test case that will start cdk with registration * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations Issues to be addressed or incidents that cause fail of job run: * CDK-216 * JBIDE-25443 * https://status.redhat.com/incidents/s7tzh47440f5 was: Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. * repair discovery itests * finish adding of mocking cdk binaries in unsupported cdk versions * update suites to run faster test classes * remove deprecated test cases * think of skipping registration and adding one test case that will start cdk with registration * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations Issues to be addressed or incidents that cause fail of job run: * CDK-216 * JBIDE-25443 > Refactor CDK itests to be more stable against CDK starts that fail sometimes > ---------------------------------------------------------------------------- > > Key: JBIDE-25438 > URL: https://issues.jboss.org/browse/JBIDE-25438 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.2.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.2.AM2 > > > Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. > * repair discovery itests > * finish adding of mocking cdk binaries in unsupported cdk versions > * update suites to run faster test classes > * remove deprecated test cases > * think of skipping registration and adding one test case that will start cdk with registration > * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations > Issues to be addressed or incidents that cause fail of job run: > * CDK-216 > * JBIDE-25443 > * https://status.redhat.com/incidents/s7tzh47440f5 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25438: ---------------------------------- Description: Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. * repair discovery itests * finish adding of mocking cdk binaries in unsupported cdk versions * update suites to run faster test classes * remove deprecated test cases * think of skipping registration and adding one test case that will start cdk with registration * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations Issues to be addressed or incidents that cause fail of job run: * CDK-216 * JBIDE-25443 was: Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. * repair discovery itests * finish adding of mocking cdk binaries in unsupported cdk versions * update suites to run faster test classes * remove deprecated test cases * think of skipping registration and adding one test case that will start cdk with registration * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations Issues to be addressed that causes fail of job run: * CDK-216 * JBIDE-25443 > Refactor CDK itests to be more stable against CDK starts that fail sometimes > ---------------------------------------------------------------------------- > > Key: JBIDE-25438 > URL: https://issues.jboss.org/browse/JBIDE-25438 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.2.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.2.AM2 > > > Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. > * repair discovery itests > * finish adding of mocking cdk binaries in unsupported cdk versions > * update suites to run faster test classes > * remove deprecated test cases > * think of skipping registration and adding one test case that will start cdk with registration > * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations > Issues to be addressed or incidents that cause fail of job run: > * CDK-216 > * JBIDE-25443 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25443) CDK itests fail on MAC os slaves with mysterious system warning dialog

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25443?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-25443: --------------------------------------- [~odockal] this means that an application crashed. I've seen it before with Eclipse crashing. But the name in this name is strange and suggests that perhaps the maven test failed in this case. Which is odd. I would assume that you would see it in the log as well. Applications crash here and there, but it should happen rarely. It happened on bigmek. I can still see the dialog there, but I don't think it should affect any tests (apart from the test that crashed). > CDK itests fail on MAC os slaves with mysterious system warning dialog > ---------------------------------------------------------------------- > > Key: JBIDE-25443 > URL: https://issues.jboss.org/browse/JBIDE-25443 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, qa > Affects Versions: 4.5.2.AM2 > Environment: MacOS > Reporter: Ondrej Dockal > Assignee: Martin Malina > Priority: Critical > Attachments: image-2017-11-29-12-52-27-497.png > > > CDK itests are sometimes blocked by system dialog (saying: JBoss Tools Test Applicaiton quit unexpectedly) and causes failures in tests. Also could be just just consequence of crashed test app... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-25438: ---------------------------------- Description: Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. * repair discovery itests * finish adding of mocking cdk binaries in unsupported cdk versions * update suites to run faster test classes * remove deprecated test cases * think of skipping registration and adding one test case that will start cdk with registration * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations Issues to be addressed that causes fail of job run: * CDK-216 * JBIDE-25443 was: Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. * repair discovery itests * finish adding of mocking cdk binaries in unsupported cdk versions * update suites to run faster test classes * remove deprecated test cases * think of skipping registration and adding one test case that will start cdk with registration * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations Issues to be addressed that causes fail of job run: * CDK-216 > Refactor CDK itests to be more stable against CDK starts that fail sometimes > ---------------------------------------------------------------------------- > > Key: JBIDE-25438 > URL: https://issues.jboss.org/browse/JBIDE-25438 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.2.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.5.2.AM2 > > > Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs. > * repair discovery itests > * finish adding of mocking cdk binaries in unsupported cdk versions > * update suites to run faster test classes > * remove deprecated test cases > * think of skipping registration and adding one test case that will start cdk with registration > * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations > Issues to be addressed that causes fail of job run: > * CDK-216 > * JBIDE-25443 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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

jbosstools-issues November 2017