April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22224) Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22224: ------------------------------------- Summary: Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer Key: JBIDE-22224 URL: https://issues.jboss.org/browse/JBIDE-22224 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Marián Labuda When I am trying to deploy a docker image via context menu of a docker image in Docker Explorer, I am prompted every time to confirm Connection dialog, although I have an established connection in OpenShift Explorer view. It's pretty annoying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22224) Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22224?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22224: ---------------------------------- Labels: docker openshift_v3 (was: ) > Prompt to confirm credentials is shown every time I want to deploy a docker image from Docker Explorer > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22224 > URL: https://issues.jboss.org/browse/JBIDE-22224 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > > When I am trying to deploy a docker image via context menu of a docker image in Docker Explorer, I am prompted every time to confirm Connection dialog, although I have an established connection in OpenShift Explorer view. It's pretty annoying. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-654: ---------------------------------- [~aileenc] That's actually good news - you definitely need java 8. Did you try my previous comment on your linux box w/ java 8? > JBDSIS stand-alone installer > ---------------------------- > > Key: JBTIS-654 > URL: https://issues.jboss.org/browse/JBTIS-654 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.1.GA > > Attachments: Capture.JPG, inst1.png > > > Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira. > Installation scenario: > {code} > 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed) > 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0.... > 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar` > 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. > 5. Accept/ respond 'Yes' and restart > 6. Select Window > Perspective > Open Perspective > Fuse Integration > {code} > A prototype installer has already been created - see: > https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22193?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22193: --------------------------------------- [~fbricon], question. {quote} So, among other things, it seems the "Run As > Docker Image build" didn't actually push the bits to the docker registry (image size is 0B) {quote} This worked for me. I then saw the new image in the Docker Explorer view and could run it. But that's something different than pushing to a registry, right? This is just a local docker build. > 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: openshift > Affects Versions: 4.3.1.Final > Reporter: Fred Bricon > Priority: Blocker > > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-678) Server requirement sometimes does not find a server type

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-678: ---------------------------------- Summary: Server requirement sometimes does not find a server type Key: JBTIS-678 URL: https://issues.jboss.org/browse/JBTIS-678 Project: JBoss Tools Integration Stack Issue Type: Bug Components: Fuse IDE, QE Affects Versions: 4.3.0.CR1 Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Fix For: 4.3.0.Final Related to _ServerKaraf.java_ from _org.jboss.tools.runtime.reddeer.impl_. It tries to select an item from new server wizard too fast (some items could be unavailable). This affects Fuse Tooling UI tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22223) Not appropriate label to start a build from build config

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22223?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22223: ---------------------------------- Description: In context menu of a build configuration in Properties view there was (in 4.3.x) menu item "Start Build" to trigger a new build from build configuration. In nightly build of JBDS a build configuration has item "Start Build ()" what seems to be strange - those parenthesis. (was: In context menu of a build configuration there was (in 4.3.x) menu item "Start Build" to trigger a new build from build config. At the moment build configuration has item "Start Build ()" what seems to be strange - those parenthesis.) > Not appropriate label to start a build from build config > -------------------------------------------------------- > > Key: JBIDE-22223 > URL: https://issues.jboss.org/browse/JBIDE-22223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > > In context menu of a build configuration in Properties view there was (in 4.3.x) menu item "Start Build" to trigger a new build from build configuration. In nightly build of JBDS a build configuration has item "Start Build ()" what seems to be strange - those parenthesis. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22223) Not appropriate label to start a build from build config

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22223?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22223: ---------------------------------- Labels: openshift_v3 (was: ) > Not appropriate label to start a build from build config > -------------------------------------------------------- > > Key: JBIDE-22223 > URL: https://issues.jboss.org/browse/JBIDE-22223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Labels: openshift_v3 > > In context menu of a build configuration in Properties view there was (in 4.3.x) menu item "Start Build" to trigger a new build from build configuration. In nightly build of JBDS a build configuration has item "Start Build ()" what seems to be strange - those parenthesis. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22223) Not appropriate label to start a build from build config

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-22223: ------------------------------------- Summary: Not appropriate label to start a build from build config Key: JBIDE-22223 URL: https://issues.jboss.org/browse/JBIDE-22223 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Alpha1 Reporter: Marián Labuda In context menu of a build configuration there was (in 4.3.x) menu item "Start Build" to trigger a new build from build config. At the moment build configuration has item "Start Build ()" what seems to be strange - those parenthesis. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-710) JBDS 9.1 GA: Document a use case for Hibernate Tooling

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-710?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-710: -------------------------------------------- > Completed conversion to md and posted as DRAFT of Portal at: https://access.redhat.com/articles/2265151 > WIP: conversion to adoc > JBDS 9.1 GA: Document a use case for Hibernate Tooling > ------------------------------------------------------ > > Key: TOOLSDOC-710 > URL: https://issues.jboss.org/browse/TOOLSDOC-710 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 9.1 GA > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Labels: Hibernate-tools > Fix For: 9.1 GA > > > Draft a use case and document it for Hibernate Tools. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3846) Create container oriented perspective

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3846?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-3846: -------------------------------- Description: At the moment we have only JBoss perspective. We should create a new, more container oriented perspective, where Docker Explorer view would be opened by default and other views should be added and aligned to satisfy user needs. Layout of perspective should be more focused on container development. (was: At the moment we have only JBoss perspective. We should create a new, more container oriented perspective, where Docker Explorer view would be opened by default. Layout of perspective should be more focused on container development.) > Create container oriented perspective > ------------------------------------- > > Key: JBDS-3846 > URL: https://issues.jboss.org/browse/JBDS-3846 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Affects Versions: 10.0.0.Alpha1 > Reporter: Marián Labuda > Priority: Critical > > At the moment we have only JBoss perspective. We should create a new, more container oriented perspective, where Docker Explorer view would be opened by default and other views should be added and aligned to satisfy user needs. Layout of perspective should be more focused on container development. -- 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 April 2016