October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23352) Deploy Docker Wizard: Default routing port selection need more info for users

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23352?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23352: ------------------------------------------ [~jeffmaury] I believe that we should add an explanatory label or info that tells the user, that when no port is selected for the route, the route will round-robin to all available ones. > Deploy Docker Wizard: Default routing port selection need more info for users > ----------------------------------------------------------------------------- > > Key: JBIDE-23352 > URL: https://issues.jboss.org/browse/JBIDE-23352 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: no_route_selected.png > > > In the wizard on wizard page Services & Routing Settings, there is a table with mapped ports. No port is selected by default , but OpenShift knows what to open. > If there is only one port mapping, we could check it by default. If there are more port mappings, we could show a label/info/description what is gonna be done under the hood, so users will know what is happening. > !no_route_selected.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4054: ----------------------------- Description: Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... * https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/ was: Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_10.0.neo... * https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.1.0.GA-buil... * https://devstudio.redhat.com/static/10.0/stable/builds/devstudio-10.1.0.G... > publish rpms + metadata to /latest/ locations so they can be easily installed by QE > ----------------------------------------------------------------------------------- > > Key: JBDS-4054 > URL: https://issues.jboss.org/browse/JBDS-4054 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: doc_writer_needed, docs_installation_guide, new_and_noteworthy > Fix For: 10.2.0.AM2 > > Attachments: rh-eclipse46-devstudio.repo > > > Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... > * https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23379) Client: setup jenkins build

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23379?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23379: ------------------------------------ Wait... in HC you said the openshift-restclient-java folks have a build in their own Jenkins. But this JIRA is titled "setup jenkins build" and you say "We should have a jenkins that builds openshift-restclient-java,..." If there's already a job somewhere, why can't we just edit that one? Why do we need a second one? > Client: setup jenkins build > --------------------------- > > Key: JBIDE-23379 > URL: https://issues.jboss.org/browse/JBIDE-23379 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Nick Boldt > Fix For: 4.4.2.AM3 > > > We should have a jenkins that builds [openshift-restclient-java|https://github.com/openshift/openshift-restclie...], deploys it to repository.jboss.org and triggers a rebuild of the [openshift client plugin|https://github.com/jbosstools/jbosstools-openshift/tree/master/plu...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4118) JBDS update site builds produces update site zip TWICE

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4118?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4118: ---------------------------------- Quick experiment with this in site/pom.xml: {code} <plugin> <groupId>tycho-p2-repository</groupId> <artifactId>archive-repository</artifactId> <version>${tychoVersion}</version> <executions> <execution> <id>default-archive-repository</id> <phase>package</phase> <goals> <goal>default-archive-repository</goal> </goals> <configuration> <skipArchive>true</skipArchive> </configuration> </execution> </executions> </plugin> {code} did not work. Error: {code} [ERROR] Plugin tycho-p2-repository:archive-repository:0.26.0 or one of its dependencies could not be resolved: Failure to find tycho-p2-repository:archive-repository:jar:0.26.0 in https://repository.sonatype.org/content/groups/sonatype-public-grid was cached in the local repository, resolution will not be reattempted until the update interval of sonatype-public-grid has elapsed or updates are forced -> [Help 1] {code} > JBDS update site builds produces update site zip TWICE > ------------------------------------------------------ > > Key: JBDS-4118 > URL: https://issues.jboss.org/browse/JBDS-4118 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM3 > > > JBDS build creates the update site zip TWICE: > {code} > [INFO] --- tycho-p2-repository-plugin:0.23.1:archive-repository (default-archive-repository) @ com.jboss.devstudio.core.site --- > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > [INFO] > [INFO] --- repository-utils:0.23.1:generate-repository-facade (generate-facade) @ com.jboss.devstudio.core.site --- > [WARNING] No /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/repository/web/site.css found; using default. > [INFO] Building zip: /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/com.jboss.devstudio.core.site-10.0.0-SNAPSHOT.zip > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23360) Select Route: Remember selected route in ambiguous routing does not work

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23360?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23360: ------------------------------------- Summary: Select Route: Remember selected route in ambiguous routing does not work (was: Remember selected route in ambiguous routing does not work) > Select Route: Remember selected route in ambiguous routing does not work > ------------------------------------------------------------------------ > > Key: JBIDE-23360 > URL: https://issues.jboss.org/browse/JBIDE-23360 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: openshift_v3, select_route > Fix For: 4.4.2.AM3 > > > When selecting Show In - Web Browser on a project with more services, routing is ambiguous. There is shown a shell "Select Route" with a checkbox "Remember selected route". This checkbox does not work. If I check it and then click OK button, I get the same prompt again next time I select Show In - Web Browser context menu item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23360) Select Route: Remember selected route in ambiguous routing does not work

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23360?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23360: ------------------------------------- Labels: openshift_v3 select_route (was: openshift_v3) > Select Route: Remember selected route in ambiguous routing does not work > ------------------------------------------------------------------------ > > Key: JBIDE-23360 > URL: https://issues.jboss.org/browse/JBIDE-23360 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: openshift_v3, select_route > Fix For: 4.4.2.AM3 > > > When selecting Show In - Web Browser on a project with more services, routing is ambiguous. There is shown a shell "Select Route" with a checkbox "Remember selected route". This checkbox does not work. If I check it and then click OK button, I get the same prompt again next time I select Show In - Web Browser context menu item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-436) Add support to copy files from container to host [EBZ#506109]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-436: --------------------------------------- Summary: Add support to copy files from container to host [EBZ#506109] Key: ERT-436 URL: https://issues.jboss.org/browse/ERT-436 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon.2 (4.6) Add support to select and copy files from live Container to a specified host directory. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23358: ------------------------------------- Fix Version/s: 4.4.x > OpenShift Explorer: Pod status is not reflecting reality > -------------------------------------------------------- > > Key: JBIDE-23358 > URL: https://issues.jboss.org/browse/JBIDE-23358 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: openshift_v3 > Fix For: 4.4.x > > Attachments: pod_status.png > > > When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". Refresh of a project or service does not help. > !pod_status.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23358?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23358: ------------------------------------------ [~mlabuda] can you please provide steps? It looks as if you deployed a local image but didnt push it to the OpenShift docker registry? > OpenShift Explorer: Pod status is not reflecting reality > -------------------------------------------------------- > > Key: JBIDE-23358 > URL: https://issues.jboss.org/browse/JBIDE-23358 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: openshift_v3 > Attachments: pod_status.png > > > When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". Refresh of a project or service does not help. > !pod_status.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23357) Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23357?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23357: ------------------------------------- Fix Version/s: 4.4.2.AM3 > Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23357 > URL: https://issues.jboss.org/browse/JBIDE-23357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > When I fill in valid image into the wizard and hit next, there is a check on existence of such image and its metadata are fetched. Problem is when I go back to the Deploy an Image wizard page and put there invalid image name. Finish button is still enabled and it allows user to use non-existing (made-up) image to deploy. It results in wrong deployment. -- 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