February 2017 - jbosstools-issues

[JBoss JIRA] (JBTIS-1035) Sync JBTIS TP w/ JBT 4.4.3

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1035?page=com.atlassian.jira.plugin... ] Paul Leacu updated JBTIS-1035: ------------------------------ Description: *Reason:* Sync with the latest Neon AM JBT core and JBT TP *Project page/sources:* *Version:* 4.4.3.AM2 *License and owner:* EPL *Original p2 repo:* *JBoss mirror:* *Include Sources:* Yes *Affected JBoss Tools components:* .DevstudioIS *Include in JBDS:* Yes (IS) *Type of dependency:* distribution *List of bundles added/removed:* {code} {code} was:Sync with the latest Neon AM JBT core and JBT TP > Sync JBTIS TP w/ JBT 4.4.3 > -------------------------- > > Key: JBTIS-1035 > URL: https://issues.jboss.org/browse/JBTIS-1035 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.2.AM1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.4.2.AM1-TP > > > *Reason:* Sync with the latest Neon AM JBT core and JBT TP > *Project page/sources:* > *Version:* 4.4.3.AM2 > *License and owner:* EPL > *Original p2 repo:* > *JBoss mirror:* > *Include Sources:* Yes > *Affected JBoss Tools components:* .DevstudioIS > *Include in JBDS:* Yes (IS) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22869: ------------------------------------- Sprint: devex #123 November 2016, devex #127 February 2017 (was: devex #123 November 2016) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22362: ------------------------------------- Sprint: devex #119 August 2016, devex #120 September 2016, devex #127 February 2017 (was: devex #119 August 2016, devex #120 September 2016) > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.3.Final > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21857: -------------------------------- Sprint: devex #123 November 2016, devex #127 February 2017 (was: devex #123 November 2016, devex #126 January 2017) > Hot code replacement doesn't work on OpenShift > ---------------------------------------------- > > Key: JBIDE-21857 > URL: https://issues.jboss.org/browse/JBIDE-21857 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM2 > > Attachments: HCRFailure.zip, code-out-of-sync.png, hot-code-replace-failed.png, jmx-connected-adapter-synchronized.png > > > When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will : > - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync > - will always fail if a method signature changed, the debugger saying JDK is out of sync > Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server) > This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23731) Integration tests: move hibernate integration tests to jbosstools/jbosstools-hibernate repo

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23731?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23731: -------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > Integration tests: move hibernate integration tests to jbosstools/jbosstools-hibernate repo > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23731 > URL: https://issues.jboss.org/browse/JBIDE-23731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, integration-tests > Affects Versions: 4.4.2.Final > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23131) Integration tests: move openshift integration tests to jbosstools/openshift repo

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23131?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23131: -------------------------------- Sprint: devex #123 November 2016, devex #127 February 2017 (was: devex #123 November 2016) > Integration tests: move openshift integration tests to jbosstools/openshift repo > -------------------------------------------------------------------------------- > > Key: JBIDE-23131 > URL: https://issues.jboss.org/browse/JBIDE-23131 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Andre Dietisheim > Assignee: Radim Hopp > Labels: integration-test > Fix For: 4.4.3.Final > > Original Estimate: 1 day > Time Spent: 4 hours > Remaining Estimate: 4 hours > > we need to move jbosstools/openshift integration tests from their [repo|https://github.com/jbosstools/jbosstools-integration-tests] to the jbosstools/openshift tools [repo|https://github.com/jbosstools/jbosstools-openshift] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23714) Implement tests for livereload remote server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23714?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23714: -------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > Implement tests for livereload remote server > -------------------------------------------- > > Key: JBIDE-23714 > URL: https://issues.jboss.org/browse/JBIDE-23714 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, livereload > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > > *configure server for remote deployments on some machine > *implement test in livereload integration tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22969: -------------------------------- Sprint: devex #123 November 2016, devex #127 February 2017 (was: devex #123 November 2016, devex #126 January 2017) > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.4.3.AM2 > > Attachments: proxy_settings.png, proxy_settings_2.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23136: -------------------------------- Sprint: devex #123 November 2016, devex #127 February 2017 (was: devex #123 November 2016, devex #126 January 2017) > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23019) Integration tests: have them running automatically, continuously

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23019?page=com.atlassian.jira.plugi... ] Radim Hopp updated JBIDE-23019: ------------------------------- Sprint: devex #123 November 2016, devex #127 February 2017 (was: devex #123 November 2016, devex #126 January 2017) > Integration tests: have them running automatically, continuously > ---------------------------------------------------------------- > > Key: JBIDE-23019 > URL: https://issues.jboss.org/browse/JBIDE-23019 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Radim Hopp > Labels: integration_tests > Fix For: 4.4.3.Final > > > The integration tests suite is very lenghty to run and should thus be run in a continuous manner on our CI. > There are several pain-points currently: > - there's no dedicated OS instance to run them against > - tests are not stable > - etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017