[JBoss JIRA] (JBTIS-1071) Reduce the number of duplicates in the update site for fuse-tooling-9.2.0.CI
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1071?page=com.atlassian.jira.plugin... ]
Paul Leacu resolved JBTIS-1071.
-------------------------------
Fix Version/s: 10.3.0.GA
Resolution: Partially Completed
Hey [~apodhrad] [~lhein]
It's unclear whether the Fuse Tooling CI builds want to continue to populate under 'integration-stack' - anyway - resolving this as partially completed. Reissue the Jira if it appears to be an issue under oxygen.
> Reduce the number of duplicates in the update site for fuse-tooling-9.2.0.CI
> ----------------------------------------------------------------------------
>
> Key: JBTIS-1071
> URL: https://issues.jboss.org/browse/JBTIS-1071
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: build, Fuse IDE
> Affects Versions: 10.2.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.3.0.GA
>
>
> The following update site
> http://download.jboss.org/jbosstools/neon/integration/updates/integration...
> contains lots of duplicated bundles.
> Moreover, there are some bundles with the same timestamp but with various build numbers
> {code}
> org.jboss.tools.fuse.transformation.editor_9.2.0.CI-v20170327-0935-B94.jar
> org.jboss.tools.fuse.transformation.editor_9.2.0.CI-v20170327-0935-B95.jar
> org.jboss.tools.fuse.transformation.editor_9.2.0.CI-v20170327-0935-B96.jar
> org.jboss.tools.fuse.transformation.editor_9.2.0.CI-v20170327-0935-B97.jar
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24491:
-------------------------------
Fix Version/s: 4.5.0.AM2
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Fix For: 4.5.0.AM2
>
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24495) Provide the equivalent to "oc new-build" && "oc start-build" && "oc expose"
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24495?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24495:
-------------------------------
Fix Version/s: 4.5.0.Final
> Provide the equivalent to "oc new-build" && "oc start-build" && "oc expose"
> ---------------------------------------------------------------------------
>
> Key: JBIDE-24495
> URL: https://issues.jboss.org/browse/JBIDE-24495
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Fix For: 4.5.0.Final
>
>
> [Helloworld MSA|https://cdn.rawgit.com/redhat-helloworld-msa/helloworld-msa/master/re...] - the reference examples for openshift - is using the command line client "oc" to create the applications in OpenShift.
> A typical approach is doing the following:
> {code}
> $ oc new-build --binary --name=hola -l app=hola
> $ mvn package; oc start-build hola --from-dir=. --follow
> $ oc new-app hola -l app=hola,hystrix.enabled=true
> $ oc expose service hola
> {code}
> For people to be able to run those with Eclipse tooling people should be able to run the equivalent in Eclipse.
> The alternative approach, that's currently available in Eclipse is imbo less evident: Users can currently build docker images locally and deploy them to OpenShift.
> The tricky part though - for now - is that the CDK is not providing access to the docker registry from the outside: the docker registry address is a private IP that's only reachable within OpenShift. Users can get around this limitation by building docker images using the docker daemon in OpenShift, which is publicly reachable. Once available in the OpenShift docker daemon it can be pushed to the OpenShift docker registry.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24498) Deploy Docker Image wizard: results dialog is not very informative
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24498?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24498:
-------------------------------
Fix Version/s: 4.5.0.AM2
> Deploy Docker Image wizard: results dialog is not very informative
> ------------------------------------------------------------------
>
> Key: JBIDE-24498
> URL: https://issues.jboss.org/browse/JBIDE-24498
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.5.0.AM2
>
> Attachments: image-2017-05-23-11-07-21-461.png
>
>
> steps to reproduce:
> # ASSERT: have a docker connection
> # ASSERT: have an OpenShift connection
> # EXEC: in "Docker Explorer": select an image and pick "Deploy to OpenShift..."
> # ASSERT: deploy docker image wizard pops up
> # EXEC: provide settings and finish the wizard
> Result:
> A dialog pops up informing you about the result of your deployment.
> !image-2017-05-23-11-07-21-461.png!
> But the dialog is not very informative, it's far from obvious what the different informations are all about:
> * If there's an error deploying (ex. you have chosen to "Push to the registry" but the registry is not reachable from the local docker daemon that holds the image that you want to deploy) the error is displayed in the title area. It's not visible at first sight that it's an error. Only by reading you're discovering it. (ex. add an error decorator)
> * There's a list of items. Nothing in the dialog tells the user what these items are.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24503) Properties: Events are hardly useable
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24503?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24503:
-------------------------------
Fix Version/s: 4.5.0.Final
> Properties: Events are hardly useable
> -------------------------------------
>
> Key: JBIDE-24503
> URL: https://issues.jboss.org/browse/JBIDE-24503
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
> Fix For: 4.5.0.Final
>
> Attachments: events-entries.png, image-2017-05-23-22-58-58-587.png
>
>
> steps:
> # EXEC: create some new application (via template or image) so that you have a build and image pulling happening
> # EXEC: select project in OpenShift Explorer and open up "Properties". In "Properties" select "Events" tab. In event entries, select some item (ex. some "Pulling" in "Reason" column), inspect the details that are displayed for it
> Result:
> !events-entries.png!
> Many entries like "Pulling", "Failed Sync", "BackOff" etc. that have larger "Message" and "Source" are hardly useable.
> * If the "Message" is very long, you have to enlarge the "Value" column a lot to be able to read the message.
> * If the "Source" is multi-line, you'll only see the opening "{", the rest is simply not displayed.
> Workaround:
> open web console where the logs are nicely displayed
> !image-2017-05-23-22-58-58-587.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months