May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22134) Docker deploy wizard: Sometimes docker image data are not shown

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22134?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22134: -------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Docker deploy wizard: Sometimes docker image data are not shown > --------------------------------------------------------------- > > Key: JBIDE-22134 > URL: https://issues.jboss.org/browse/JBIDE-22134 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard. Environment variables, exposed ports etc. Unfortunately I don't have a way to reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet, I have not spotted this at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20577) Allow setting exploded or zipped on per-module basis

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20577?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20577: -------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Allow setting exploded or zipped on per-module basis > ---------------------------------------------------- > > Key: JBIDE-20577 > URL: https://issues.jboss.org/browse/JBIDE-20577 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > While in the past, we automatically zipped up dependent utility projects, we recently switched to allowing exploded utility projects for appserver versions that suppoort it. Some users have determined this is slower for their usecase, and we should investigate giving users more control over this feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20338) Investigate adding filesystem deployment integration tests against running servers

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20338?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20338: -------------------------------- Fix Version/s: 4.4.0.Alpha2 (was: 4.4.0.Alpha1) > Investigate adding filesystem deployment integration tests against running servers > ---------------------------------------------------------------------------------- > > Key: JBIDE-20338 > URL: https://issues.jboss.org/browse/JBIDE-20338 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > See JBIDE-15250 for more background. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-21634. ------------------------------ In that case... Verified on JBDS 10.0.0.Alpha1. Closing. Thanks for very quick clarification! > Explorer, Properties: Allow a user to scale their deployment > ------------------------------------------------------------ > > Key: JBIDE-21634 > URL: https://issues.jboss.org/browse/JBIDE-21634 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > > The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of: > 1. deployment (replication controller) > 2. eclipse view of a deployment (service) -> walk back to the currrent deployment > 3. pod -> walk back to the current deployment > updating 'spec.replicas' causes a new pods to spin up -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20937) Create resource(s) from json

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20937: -------------------------------- Sprint: (was: devex #113 April 2016) > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha2 > > Attachments: cakephp-example-imagestream.json, cakephp-example-service.json, New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png > > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20937) Create resource(s) from json

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20937: -------------------------------- Sprint: devex #114 May 2017 > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha2 > > Attachments: cakephp-example-imagestream.json, cakephp-example-service.json, New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png > > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21634: --------------------------------------- You are correct; we did not implement 'scaling' starting with a pod. You can scale: * using the context menu on a service which is the first node below the project. * From the property tabs of a deployment(replication controller) and deploymentconfig > Explorer, Properties: Allow a user to scale their deployment > ------------------------------------------------------------ > > Key: JBIDE-21634 > URL: https://issues.jboss.org/browse/JBIDE-21634 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > > The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of: > 1. deployment (replication controller) > 2. eclipse view of a deployment (service) -> walk back to the currrent deployment > 3. pod -> walk back to the current deployment > updating 'spec.replicas' causes a new pods to spin up -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21527) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21527?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-21527. ------------------------------ Verified in JBDS 10.0.0.Alpha1. Closing. > Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH > ------------------------------------------------------------------------------------- > > Key: JBIDE-21527 > URL: https://issues.jboss.org/browse/JBIDE-21527 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: openshift_v3, preferences > Fix For: 4.4.0.Alpha1 > > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20023) Show in browser: missing project/server that we're listing the routes of

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20023?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-20023. ------------------------------ Verified in JBDS 10.0.0.Alpha1. Closing. > Show in browser: missing project/server that we're listing the routes of > ------------------------------------------------------------------------ > > Key: JBIDE-20023 > URL: https://issues.jboss.org/browse/JBIDE-20023 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: help_wanted, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: show-in-browser-routes.png > > > how to reproduce: > # ASSERT: make sure that you have a project with several routes on a v3 OpenShift server > # ASSERT: make sure that you have a connetion in explorer to this server > # EXEC: in Explorer: unfold Routes and pick "Show in->Web Browser" > Result: > !show-in-browser-routes.png! > A dialog requiring to select the route that you want to open up in the browser pops up. The dialog wont tell you what server, project the routes are listed for. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-21634: ------------------------------------ [~jcantrill]Just to be sure... You discarded the idea of scaling by menu on pods, right? And the only places to do that is deployment config, and deployment (in properties) and route in explorer (the thing with arrows in icon). Am I missing something? > Explorer, Properties: Allow a user to scale their deployment > ------------------------------------------------------------ > > Key: JBIDE-21634 > URL: https://issues.jboss.org/browse/JBIDE-21634 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > > The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of: > 1. deployment (replication controller) > 2. eclipse view of a deployment (service) -> walk back to the currrent deployment > 3. pod -> walk back to the current deployment > updating 'spec.replicas' causes a new pods to spin up -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016