[JBoss JIRA] (JBIDE-22165) Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22165:
--------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.x)
Story Points: 5
Sprint: devex #114 May 2017
> Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22165
> URL: https://issues.jboss.org/browse/JBIDE-22165
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Thomas Mäder
> Labels: deploy_docker_wizard, docker, openshift_v3
> Fix For: 4.4.0.Alpha2
>
>
> I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself...
> At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22165) Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22165?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22165:
-----------------------------------
Assignee: Thomas Mäder
> Deploy Docker wizard: Check "Add Route" checkbox for exposing services of docker image by default
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22165
> URL: https://issues.jboss.org/browse/JBIDE-22165
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Thomas Mäder
> Labels: deploy_docker_wizard, docker, openshift_v3
> Fix For: 4.4.x
>
>
> I think usually users would like to expose their services of a docker image being deployed to OpenShift. In the Deploy Image to OpenShift wizard we have a wizard page where mapping of ports is happening and also exposing of services to routes by checking a checkbox "Add Route" is placed there. By default we have this checkbox unchecked, but maybe we should enable it by default. In my humble opinion in many use case there will be an existing docker image of some application and user would like to deploy it to OpenShift and check application whether it is working or use some features of OpenShift itself...
> At the moment we don't have enabled exposing of OpenShift resources in tooling and therefore if user by accident or intentionally click on Finish button in Deploy Image to OpenShift wizard one page earlier (the one where env. vars, scaling and data volumes are located), it produce a running pod with service, but there is no route and it force user to swich to command line to use oc to expose a service to get a route.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-20915:
----------------------------------
Story Points: 1
> HTML Page is not refreshed after page is changed in web browser with enabled LiveReload
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-20915
> URL: https://issues.jboss.org/browse/JBIDE-20915
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.3.0.CR2
> Environment: JBDS 9.0.0.GA-v20150925-1252-B116
> Reporter: Vlado Pakan
> Assignee: Xavier Coulon
> Labels: documentation
> Fix For: 4.4.0.Alpha2
>
>
> 1. Import HTML 5 project from JBoss Central
> 2. Run it on server
> 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server'
> ASSERT: index.html page is opened in system web browser
> 4. Make some changes to opened page and save them.
> ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser.
> Repeat step 4. couple of times
> ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-18963) when whatsnew index generation is run on files that refer components that does not exist an error message containing what component is at fault should be printed
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18963?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-18963:
----------------------------------
Fix Version/s: LATER
(was: 4.4.x)
Moving to {{LATER}} because of other priorities.
> when whatsnew index generation is run on files that refer components that does not exist an error message containing what component is at fault should be printed
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18963
> URL: https://issues.jboss.org/browse/JBIDE-18963
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: website
> Affects Versions: 4.2.3.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Fix For: LATER
>
>
> today when having invalid components you get something like:
> {code}
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65:in `block (4 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:64:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:64:in `block (3 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:29:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:29:in `block (2 levels) in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:27:in `each'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:27:in `block in singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65533:in `instance_eval'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65533:in `singletonclass'
> /Users/max/code/jbosstools/jbosstools-website/documentation/whatsnew/index.html.haml:65531:in `__tilt_70190394039780'
> {code}
> as found in https://github.com/jbosstools/jbosstools-website/pull/311/files
> the logic is all embedded in haml leaving no room for proper error handling.
> should do some basic asserts in the pipeline for that ids actually exists in components.yml or at least just use component id as fall back name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months