October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-204: ------------------------------ Sprint: devex #118 July 2016, devex #120 September 2016, devex #122 October 2016 (was: devex #118 July 2016, devex #120 September 2016, devex #121 October 2016) > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22451) Tests: Improve test coverage in OpenShift

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22451?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22451: ----------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Tests: Improve test coverage in OpenShift > ----------------------------------------- > > Key: JBIDE-22451 > URL: https://issues.jboss.org/browse/JBIDE-22451 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > > Test coverage in OpenShift is far too poor. We have to increase it dramatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23057) Integration tests: test import project in server adapter wizard

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23057?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23057: ----------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Integration tests: test import project in server adapter wizard > --------------------------------------------------------------- > > Key: JBIDE-23057 > URL: https://issues.jboss.org/browse/JBIDE-23057 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM3 > > > JBIDE-22621 allows the user to import a project in the server adapter wizard. We should add an integration test for this scenarion in CreateServerAdapterTest -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23005) Server Adapter: Stuck on creating/publishing

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23005: ----------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Server Adapter: Stuck on creating/publishing > -------------------------------------------- > > Key: JBIDE-23005 > URL: https://issues.jboss.org/browse/JBIDE-23005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM3 > > Attachments: stucked_server_adapter > > > When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23019?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23019: ----------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > 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: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.2.AM2 > > > 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 (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22816: ----------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Create application from image (or builder) may lead to update being detected > ---------------------------------------------------------------------------- > > Key: JBIDE-22816 > URL: https://issues.jboss.org/browse/JBIDE-22816 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Fix For: 4.4.2.AM3 > > > When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23135) Verify every EAP 7.1 devel/candidate works with eap7x Server adapter

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23135?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23135: ----------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Verify every EAP 7.1 devel/candidate works with eap7x Server adapter > -------------------------------------------------------------------- > > Key: JBIDE-23135 > URL: https://issues.jboss.org/browse/JBIDE-23135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Alexey Kazakov > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.2.AM2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

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

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22869: ----------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 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.2.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 (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18912) Custom deploy dir with remote server using filesystem operations does not work

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18912?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18912: ----------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Custom deploy dir with remote server using filesystem operations does not work > ------------------------------------------------------------------------------ > > Key: JBIDE-18912 > URL: https://issues.jboss.org/browse/JBIDE-18912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.1.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: help_wanted > Fix For: 4.4.2.AM2 > > > This is a follow up of JBIDE-17180 and JBIDE-13445 which added the option to add a custom deployment directory if your remote server is using filesystem operations (for management api it's not relevant since the deployment happens directly, no directory is used). > Unfortunately it does not work. It seems I haven't really tried it when reviewing those other JIRAs because there were other obstacles. > I tried this several times and still could not get it to work. > Perhaps it might be worth to try and get this in the final 4.2.1.Final build? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21065) Server host name address should not be defaulted during server adapter creation

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21065?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21065: ----------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Server host name address should not be defaulted during server adapter creation > ------------------------------------------------------------------------------- > > Key: JBIDE-21065 > URL: https://issues.jboss.org/browse/JBIDE-21065 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.4.2.AM2 > > > I've noticed that when I create a server adapter and I give it an IP address as the hostname, the hostname remains the default value, ie, {{localhost}}. > This is annoying in the case where I want to connect to a VM running on my own host (eg, a VM running Docker). In this particular case, I set the hostname at something like {{192.168.99.100}} but it is reverted as {{localhost}} which gives {{127.0.0.1}} as the primary IP address. As a consequence, the server adapter fails to connect to the server since it uses the wrong IP address. > Note that the host name can be changed for good in the Server Configuration Editor _after_ its creation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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