February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21641) OpenShift Explorer : running Builds should use the standard build execution icon

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21641?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21641: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > OpenShift Explorer : running Builds should use the standard build execution icon > -------------------------------------------------------------------------------- > > Key: JBIDE-21641 > URL: https://issues.jboss.org/browse/JBIDE-21641 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.1.CR1 > > > When a build is started, it shows up in the OpenShift explorer with the File icon. It should use a more standard eclipse build icon -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21750) OpenShift Explorer : running Builds should use the standard build execution icon

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21750?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21750: ---------------------------------- Fix Version/s: (was: 4.3.1.CR1) > OpenShift Explorer : running Builds should use the standard build execution icon > -------------------------------------------------------------------------------- > > Key: JBIDE-21750 > URL: https://issues.jboss.org/browse/JBIDE-21750 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > When a build is started, it shows up in the OpenShift explorer with the File icon. It should use a more standard eclipse build icon -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21650) Make Import OS3 Application more context-oriented

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21650?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21650. --------------------------------- Verified on nightly build of JBT with OpenShift tooling B192. > Make Import OS3 Application more context-oriented > ------------------------------------------------- > > Key: JBIDE-21650 > URL: https://issues.jboss.org/browse/JBIDE-21650 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: import_wizard, openshift_v3 > Fix For: 4.3.1.CR1 > > > Currently we don't make difference from where Import Application... context menu item in OpenShift Explorer view is invoked. If a connection contains 2 and more projects, and at least 2 of those projects contains a build config, there are always listed all projects with build configs in Import OpenShift Application wizard no matter what. Even if I have selected a specific service or project, invoked Import Application wizard lists all projects and build configs. It would be nice to have it more context oriented - when select Import Application... context menu item on a specific service, build config related to this service should be preselected in wizard (maybe only project where the service is located should be listed and its build configs with selected the selected one). If opened via context menu of a project, project should be preselected (maybe only project with its build config could be visible). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21658) Property sheet cells are editable

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21658?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21658. --------------------------------- Verified on nightly build of JBT with OpenShift tooling B192. > Property sheet cells are editable > --------------------------------- > > Key: JBIDE-21658 > URL: https://issues.jboss.org/browse/JBIDE-21658 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.x > Environment: Boss Openshift UI Plugin Version: 3.1.0.CR1-v20160202-0335-B166 > Reporter: Steve Speicher > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1 > > Attachments: Screen Shot 2016-02-06 at 9.03.05 AM.png > > > When I bring up the property sheet, values are editable but I can't really edit them. It would be good if users were disallowed from changing values (like the property name field is restricted) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21660) openshift 3 is not inlcuded by default in JBoss Tools

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21660?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21660. --------------------------------- Closed as rejected. > openshift 3 is not inlcuded by default in JBoss Tools > ----------------------------------------------------- > > Key: JBIDE-21660 > URL: https://issues.jboss.org/browse/JBIDE-21660 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace, openshift, updatesite > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.CR1 > > > installing latest release and I don't get OpenShift 3 into default install. > The goal was to get openshift included by default - is it ready for it ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21669) Enable easy scaling of OpenShift 3 applications

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21669?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21669. --------------------------------- Closed as a duplicate. > Enable easy scaling of OpenShift 3 applications > ----------------------------------------------- > > Key: JBIDE-21669 > URL: https://issues.jboss.org/browse/JBIDE-21669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > Fix For: 4.3.1.CR1 > > > In Web-UI there is a spinner to set amount of running pods and we don't have something similar and user friendly in our tooling. At the moment to scale up/down an OpenShift 3 application, it is required to modify replication controller (which is a bit buggy see JBIDE-21665 and whole work flow is not quite user friendly). It would be nice to have a context menu item in context menu of a service, something like "Scale Up" enabled all the time and "Scale Down" in case there are at least 2 pods running. Or it could be "Add Pod" "Remove Pod" or something similar. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21675) Text editor of OpenShift resource should provide more information about resource

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21675?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21675. --------------------------------- Great, thanks! Verified on nightly build of JBT with OpenShift tooling B192. > Text editor of OpenShift resource should provide more information about resource > -------------------------------------------------------------------------------- > > Key: JBIDE-21675 > URL: https://issues.jboss.org/browse/JBIDE-21675 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > When I choose Edit.. in context menu of an OpenShift resource, its open a new text editor with JSON of resource. Currently name/title of such text editor is in format "resource type : resource name" (example "Image Stream : bug-consolidator"). If I have more such editor opened, e.g. I have a staging project, testing project and production project with same resource name, it is difficult to find out to which resource the content of editor belongs (it is possible but it requires to read content and find namespace or selflink which contain project name). > It would be nice if editor of OpenShift resource would contain at least project name in its name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21715) Unable to deploy image because a deployment (replication controller) does not exist

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21715?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21715. --------------------------------- > Unable to deploy image because a deployment (replication controller) does not exist > ----------------------------------------------------------------------------------- > > Key: JBIDE-21715 > URL: https://issues.jboss.org/browse/JBIDE-21715 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.1.CR1 > > > Deploying an image creates a set of resources but trying to manually trigger a deployment throws an exception: http://screencast.com/t/gz8quBbAboGg > This presumably could be a case where we are trying to tigger assuming a deployment exists but one doesnt because: > a) its building and hasnt triggered one yet > b) the built image exists but there is some other reason that prevents the imagechangetrigger > We should still be able to trigger a build using the dc provided OpenShift is able to access the image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21715) Unable to deploy image because a deployment (replication controller) does not exist

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21715?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21715: --------------------------------------- Verified on nightly build of JBT with OpenShift tooling B190. > Unable to deploy image because a deployment (replication controller) does not exist > ----------------------------------------------------------------------------------- > > Key: JBIDE-21715 > URL: https://issues.jboss.org/browse/JBIDE-21715 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.1.CR1 > > > Deploying an image creates a set of resources but trying to manually trigger a deployment throws an exception: http://screencast.com/t/gz8quBbAboGg > This presumably could be a case where we are trying to tigger assuming a deployment exists but one doesnt because: > a) its building and hasnt triggered one yet > b) the built image exists but there is some other reason that prevents the imagechangetrigger > We should still be able to trigger a build using the dc provided OpenShift is able to access the image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21749) OpenShift Server Adapter creation Wizard does not fit in 13" screen

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21749?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-21749: --------------------------------------- I confirm that the wizard page now renders properly on my 13" screen. > OpenShift Server Adapter creation Wizard does not fit in 13" screen > ------------------------------------------------------------------- > > Key: JBIDE-21749 > URL: https://issues.jboss.org/browse/JBIDE-21749 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1 > > Attachments: Screenshot 2016-02-23 18.55.52.png > > > The Server settings page is too high for my 13" screen: the "default route" section is barely visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016