June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22458) JBoss Help should use DCP v2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22458?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22458: -------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/510, https://github.com/jbosstools/jbosstools-central/pull/381 (was: https://github.com/jbosstools/jbosstools-base/pull/510) > JBoss Help should use DCP v2 > ----------------------------- > > Key: JBIDE-22458 > URL: https://issues.jboss.org/browse/JBIDE-22458 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common/jst/core > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha3 > > > The DCPv1 search service is being phased out in favor of DCPv2. The JBoss Help feature needs to migrate to v2 as well. > - the search url needs to be changed to http://dcp2.jboss.org/v2/rest/search?size=100&query={expression}&sys_type... in org.jboss.tools.central/plugin.xml > - The JSON Parser needs to be updated to the new result format (fields are returned as arrays, we need to get the 1st element now). See https://github.com/jbosstools/jbosstools-base/blob/e0b10e225f070bc11aa1bf... > Bad news is JBDS 9/ JBT 4.3 help search will break as soon as DCPv1 is decommissioned, since the search URL is hard coded in the plugin.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22458) JBoss Help should use DCP v2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22458?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22458: ------------------------------------- https://github.com/jbosstools/jbosstools-central/pull/381 is for JBoss Central > JBoss Help should use DCP v2 > ----------------------------- > > Key: JBIDE-22458 > URL: https://issues.jboss.org/browse/JBIDE-22458 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common/jst/core > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha3 > > > The DCPv1 search service is being phased out in favor of DCPv2. The JBoss Help feature needs to migrate to v2 as well. > - the search url needs to be changed to http://dcp2.jboss.org/v2/rest/search?size=100&query={expression}&sys_type... in org.jboss.tools.central/plugin.xml > - The JSON Parser needs to be updated to the new result format (fields are returned as arrays, we need to get the 1st element now). See https://github.com/jbosstools/jbosstools-base/blob/e0b10e225f070bc11aa1bf... > Bad news is JBDS 9/ JBT 4.3 help search will break as soon as DCPv1 is decommissioned, since the search URL is hard coded in the plugin.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22458) JBoss Help should use DCP v2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22458?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22458: ----------------------------------- Fix Version/s: 4.4.0.Alpha3 Story Points: 1 Sprint: devex #115 May 2016 Assignee: Fred Bricon > JBoss Help should use DCP v2 > ----------------------------- > > Key: JBIDE-22458 > URL: https://issues.jboss.org/browse/JBIDE-22458 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, common/jst/core > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha3 > > > The DCPv1 search service is being phased out in favor of DCPv2. The JBoss Help feature needs to migrate to v2 as well. > - the search url needs to be changed to http://dcp2.jboss.org/v2/rest/search?size=100&query={expression}&sys_type... in org.jboss.tools.central/plugin.xml > - The JSON Parser needs to be updated to the new result format (fields are returned as arrays, we need to get the 1st element now). See https://github.com/jbosstools/jbosstools-base/blob/e0b10e225f070bc11aa1bf... > Bad news is JBDS 9/ JBT 4.3 help search will break as soon as DCPv1 is decommissioned, since the search URL is hard coded in the plugin.xml -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22473) Environment Var Wizard: Cannot remove env vars

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22473?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-22473: --------------------------------------- The other thing to remember is if the image defines this variable, removing it will have no affect. > Environment Var Wizard: Cannot remove env vars > ---------------------------------------------- > > Key: JBIDE-22473 > URL: https://issues.jboss.org/browse/JBIDE-22473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Labels: env_var_wizard, openshift_v3 > Fix For: 4.4.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20601) deploy to openshift only have one "add route" checkbox for multiple services?

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20601?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20601: ------------------------------------- Fix Version/s: 4.4.0.Alpha3 (was: 4.4.x) > deploy to openshift only have one "add route" checkbox for multiple services? > ----------------------------------------------------------------------------- > > Key: JBIDE-20601 > URL: https://issues.jboss.org/browse/JBIDE-20601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.0.Alpha3 > > > On the services page several ports are listed and then a "Add route" label is shown. > I assume this actually means Add route*s* for all services, but seems this should be just a checkbox in the table and with option to override the exposed port value. > Similar to what docker tools does. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20601) deploy to openshift only have one "add route" checkbox for multiple services?

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20601?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20601: ------------------------------------- Labels: openshift_v3 (was: ) > deploy to openshift only have one "add route" checkbox for multiple services? > ----------------------------------------------------------------------------- > > Key: JBIDE-20601 > URL: https://issues.jboss.org/browse/JBIDE-20601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.0.Alpha3 > > > On the services page several ports are listed and then a "Add route" label is shown. > I assume this actually means Add route*s* for all services, but seems this should be just a checkbox in the table and with option to override the exposed port value. > Similar to what docker tools does. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20601) deploy to openshift only have one "add route" checkbox for multiple services?

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20601?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20601: ------------------------------------------ merged into master. > deploy to openshift only have one "add route" checkbox for multiple services? > ----------------------------------------------------------------------------- > > Key: JBIDE-20601 > URL: https://issues.jboss.org/browse/JBIDE-20601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Jeff Cantrill > Fix For: 4.4.x > > > On the services page several ports are listed and then a "Add route" label is shown. > I assume this actually means Add route*s* for all services, but seems this should be just a checkbox in the table and with option to override the exposed port value. > Similar to what docker tools does. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-725) Fix Model Wizard Test

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-725?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-725. ----------------------------------- pushed to master > Fix Model Wizard Test > --------------------- > > Key: JBTIS-725 > URL: https://issues.jboss.org/browse/JBTIS-725 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.1.Final > > > Fix model names in new Model Wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3282: --------------------------------- Priority: Critical (was: Blocker) > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: documentation, openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Critical > Labels: screencast > Fix For: 10.0.0.Alpha3 > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22193) Can't deploy locally built docker images

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22193?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22193: ----------------------------------- Priority: Critical (was: Blocker) > Can't deploy locally built docker images > ---------------------------------------- > > Key: JBIDE-22193 > URL: https://issues.jboss.org/browse/JBIDE-22193 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift, upstream > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.0.Alpha3 > > > I can't deploy locally built docker images, pushed to the CDK docker registry, to OpenShift > Trying to adapt the steps from https://github.com/redhat-developer-tooling/openshift-vagrant#how-to-run-... to Eclipse, I can't seem to be able to deploy anything > Here's what the CLI generates from > {quote} > eval "$(vagrant service-manager env docker)" > $ oc login 10.1.2.2:8443 -u openshift-dev -p devel > Login successful. > $ oc new-project my-ghost > Now using project "my-ghost" on server "https://10.1.2.2:8443". > $ docker pull ghost > $ docker tag ghost hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost > $ docker login -u openshift-dev -p `oc whoami -t` -e foo(a)bar.com hub.openshift.rhel-cdk.10.1.2.2.xip.io > $ docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost > $ oc new-app --image-stream=ghost --name=ghost > $ oc expose service ghost --hostname=my-ghost-blog.rhel-cdk.10.1.2.2.xip.io > {quote} > Deployment Config > {noformat} > { > "kind" : "DeploymentConfig", > "apiVersion" : "v1", > "metadata" : { > "name" : "ghost", > "namespace" : "my-ghost", > "selfLink" : "/oapi/v1/namespaces/my-ghost/deploymentconfigs/ghost", > "uid" : "a7dafee5-03c8-11e6-82b7-525400ac6ae1", > "resourceVersion" : "29849", > "creationTimestamp" : "2016-04-16T11:45:02Z", > "labels" : {"app" : "ghost"}, > "annotations" : {"openshift.io/generated-by" : "OpenShiftNewApp"} > }, > "spec" : { > "strategy" : { > "type" : "Rolling", > "rollingParams" : { > "updatePeriodSeconds" : 1, > "intervalSeconds" : 1, > "timeoutSeconds" : 600, > "maxUnavailable" : "25%", > "maxSurge" : "25%" > } > }, > "triggers" : [ > {"type" : "ConfigChange"}, > { > "type" : "ImageChange", > "imageChangeParams" : { > "automatic" : true, > "containerNames" : ["ghost"], > "from" : { > "kind" : "ImageStreamTag", > "namespace" : "my-ghost", > "name" : "ghost:latest" > }, > "lastTriggeredImage" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8" > } > } > ], > "replicas" : 1, > "selector" : { > "app" : "ghost", > "deploymentconfig" : "ghost" > }, > "template" : { > "metadata" : { > "labels" : { > "app" : "ghost", > "deploymentconfig" : "ghost" > }, > "annotations" : { > "openshift.io/container.ghost.image.entrypoint" : "[\"/entrypoint.sh\",\"npm\",\"start\"]", > "openshift.io/generated-by" : "OpenShiftNewApp" > } > }, > "spec" : { > "volumes" : [{"name" : "ghost-volume-1"}], > "containers" : [{ > "name" : "ghost", > "image" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8", > "ports" : [{ > "containerPort" : 2368, > "protocol" : "TCP" > }], > "volumeMounts" : [{ > "name" : "ghost-volume-1", > "mountPath" : "/var/lib/ghost" > }], > "terminationMessagePath" : "/dev/termination-log", > "imagePullPolicy" : "Always" > }], > "restartPolicy" : "Always", > "terminationGracePeriodSeconds" : 30, > "dnsPolicy" : "ClusterFirst" > } > } > }, > "status" : { > "latestVersion" : 1, > "details" : {"causes" : [{"type" : "ConfigChange"}]} > } > } > {noformat} > Image Stream > {noformat} > { > "kind" : "ImageStream", > "apiVersion" : "v1", > "metadata" : { > "name" : "ghost", > "namespace" : "my-ghost", > "selfLink" : "/oapi/v1/namespaces/my-ghost/imagestreams/ghost", > "uid" : "98a32494-03c8-11e6-82b7-525400ac6ae1", > "resourceVersion" : "29842", > "creationTimestamp" : "2016-04-16T11:44:37Z", > "annotations" : {"openshift.io/image.dockerRepositoryCheck" : "2016-04-16T11:44:37Z"} > }, > "status" : { > "dockerImageRepository" : "172.30.178.20:5000/my-ghost/ghost", > "tags" : [{ > "tag" : "latest", > "items" : [{ > "created" : "2016-04-16T11:44:37Z", > "dockerImageReference" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8", > "image" : "sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8" > }] > }] > } > } > {noformat} > When following these steps in Eclipse, no deployment occurs. Going to the web console et clicking deploy on the Deployment, no image is found to deploy. > {quote} > - Clone https://github.com/burrsutter/cdk_helloworlds/ > - import java/wildflyswarm_helloworld as a Maven Project > - Run a Maven build (Run As > Maven > package) > - Edit Dockerfile: replace `FROM rhel7` with `FROM centos` > - right click on Dockerfile > Run As > Docker Image build > - Select `CDK Server Adapter at localhost` connection > - Repository Name : hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm > - from OpenShift explorer, create a fredo project > - In OpenShift explorer, right-click the fredo project and Deploy Docker Image... > - select hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm:latest for the image > - swarm as resource name > - click next > - Deployment configuration & scalability page displays, click next > - click add route button, click finish > - resources are created, but no deployment happens > {quote} > Here are the resources created from Eclipse: > Deployment Config > {noformat} > { > "metadata" : { > "name" : "swarm", > "namespace" : "fredo", > "selfLink" : "/oapi/v1/namespaces/fredo/deploymentconfigs/swarm", > "uid" : "2e9d1df4-03cc-11e6-82b7-525400ac6ae1", > "resourceVersion" : "30206", > "creationTimestamp" : "2016-04-16T12:10:17Z", > "labels" : {"deploymentconfig" : "swarm"}, > "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"} > }, > "spec" : { > "strategy" : { > "type" : "Rolling", > "rollingParams" : { > "updatePeriodSeconds" : 1, > "intervalSeconds" : 1, > "timeoutSeconds" : 600, > "maxUnavailable" : "25%", > "maxSurge" : "25%" > } > }, > "triggers" : [ > {"type" : "ConfigChange"}, > { > "type" : "ImageChange", > "imageChangeParams" : { > "automatic" : true, > "containerNames" : ["swarm"], > "from" : { > "kind" : "ImageStreamTag", > "name" : "swarm:latest" > } > } > } > ], > "replicas" : 1, > "selector" : {"deploymentconfig" : "swarm"}, > "template" : { > "metadata" : {"labels" : {"deploymentconfig" : "swarm"}}, > "spec" : { > "containers" : [{ > "name" : "swarm", > "image" : "fredo/swarm:latest", > "ports" : [{ > "name" : "8080-tcp", > "containerPort" : 8080, > "protocol" : "TCP" > }], > "terminationMessagePath" : "/dev/termination-log", > "imagePullPolicy" : "Always" > }], > "restartPolicy" : "Always", > "terminationGracePeriodSeconds" : 30, > "dnsPolicy" : "ClusterFirst" > } > } > }, > "apiVersion" : "v1", > "kind" : "DeploymentConfig" > } > {noformat} > Image Stream > {noformat} > { > "metadata" : { > "name" : "swarm", > "namespace" : "fredo", > "selfLink" : "/oapi/v1/namespaces/fredo/imagestreams/swarm", > "uid" : "2e42dfc8-03cc-11e6-82b7-525400ac6ae1", > "resourceVersion" : "30202", > "creationTimestamp" : "2016-04-16T12:10:16Z", > "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"} > }, > "spec" : {"dockerImageRepository" : "hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm"}, > "status" : {"dockerImageRepository" : "172.30.178.20:5000/fredo/swarm"}, > "apiVersion" : "v1", > "kind" : "ImageStream" > } > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016