June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20705) Click on a webhook URL in Webhook triggers shell automatically copy webhook to clipboard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20705?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20705: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Click on a webhook URL in Webhook triggers shell automatically copy webhook to clipboard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-20705 > URL: https://issues.jboss.org/browse/JBIDE-20705 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.5.0.Final > > Attachments: webhook.png > > > In Webhook triggers shell, opened via context menu of a build config, there are 2 text widgets containing generic and github webhook. > !webhook.png! > After click on a webhook text, the whole text is selected and its automatically copied to clipboard. There is also a notification text upon copying to clipboard shown close to the text widget containing a webhook URL. > Webhook URL should be copied only after click on a button with label "Copy to clipboard" which is located next to the text field containing a webhook URL. Otherwise this button miss reason to exists and it is a bit annoying for me to have URL automatically selected and copied to clipboard every time I click on a text. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20730) Displaying of a project in OpenShift Explorer view is not consistent

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20730?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20730: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Displaying of a project in OpenShift Explorer view is not consistent > -------------------------------------------------------------------- > > Key: JBIDE-20730 > URL: https://issues.jboss.org/browse/JBIDE-20730 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Labels: explorer, openshift_v3 > Fix For: 4.5.0.Final > > > OpenShift 3 project is displayed a bit tricky in OpenShift Explorer view. If project has only project name, then project name is shown as normal text in OpenShift Explorer view under an OpenShift 3 connection. But if a project has set also an optional attribute displayName, then this name is used as a normal text under an OpenShift 3 connection and it's name is used only as a decorated text in parenthesis. Example: > Project 01 has name: project01 > Project 02 has name: project02 and displayName: projectName02 > In OpenShift Explorer view are those projects shown as > project01 > projectName02 (project02) > One could think that project01 and projectName02 are the same attribute of a project, but it's not. I think we could and should show projects like this: > project01 (project01) > projectName02 (project02) > because default value for a displayName is attribute name. In that case it would be consistent and user would not be confused. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21479) Explorer: Display deployment details like web console

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21479?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21479: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Explorer: Display deployment details like web console > ----------------------------------------------------- > > Key: JBIDE-21479 > URL: https://issues.jboss.org/browse/JBIDE-21479 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Labels: openshift_deployment_view, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21652) We should make OS 3 application status more visible for users

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21652?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21652: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > We should make OS 3 application status more visible for users > ------------------------------------------------------------- > > Key: JBIDE-21652 > URL: https://issues.jboss.org/browse/JBIDE-21652 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Alexey Kazakov > Fix For: 4.5.0.Final > > > Currently it can be confusing for users when an application is not available because it's building. > We should think about our options, how we could improve visibility of the application status in both OS Explorer and Servers view (for OS server adapters). > For example we could add a status line for an "application" node (or even for a project?) and show "Building..." or something if any of its services is building. We also could use a red font for such statuses. An gif icon would be ideal but I'm not sure it's technically possible. > OS Server adapter is a separate story but we need to add status for it too. Maybe it's worth a separate issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21655) Tests: add tests to server adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21655?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21655: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Tests: add tests to server adapter > ---------------------------------- > > Key: JBIDE-21655 > URL: https://issues.jboss.org/browse/JBIDE-21655 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20573) OpenShift Explorer: decorate project showing last build/deployment failed/succeeded

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20573?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20573: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > OpenShift Explorer: decorate project showing last build/deployment failed/succeeded > ----------------------------------------------------------------------------------- > > Key: JBIDE-20573 > URL: https://issues.jboss.org/browse/JBIDE-20573 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Labels: explorer, openshift_v3 > Fix For: 4.5.0.Final > > > As reported by [~sspeiche] (or was it [~crobson]?), it'd be nice to have a visual clue of a project state, in the OpenShift Explorer. We should display the last pod status (build failed or deployment succeeded) next to a project's node -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23899) Refactor the OpenShift server adapter to meet new needs (Vert.x, Swarm, ...)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23899?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23899: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Refactor the OpenShift server adapter to meet new needs (Vert.x, Swarm,...) > --------------------------------------------------------------------------- > > Key: JBIDE-23899 > URL: https://issues.jboss.org/browse/JBIDE-23899 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.Final > > > The current version of the OpenShift server adapter has some drawbacks: > - code is linked with EAP/Wildfly on one side and NodeJS on the other > - apart from those two stacks, we don't support others (FUSE, Vert.x,Swarm,...) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23901) Support Vert.x stack

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23901?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23901: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Support Vert.x stack > -------------------- > > Key: JBIDE-23901 > URL: https://issues.jboss.org/browse/JBIDE-23901 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.Final > > > We should provide suppport for Vert.x stack in OpenShift tooling -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20036) As I user I want to be able to add image streams to my project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20036?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20036: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > As I user I want to be able to add image streams to my project > -------------------------------------------------------------- > > Key: JBIDE-20036 > URL: https://issues.jboss.org/browse/JBIDE-20036 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.5.0.Final > > > When creating a new application via templates I am required to have the docker images (base builder image etc.) to be available. Otherwise the build wont succeed. > You can see this in the instrcutions for the eap templates where the steps to create an app via those templates are 2: create the image streams & create the app via the templates: > https://github.com/adietish/application-templates/blob/master/README.md > {code} > $ osc create -n yourproject -f jboss-image-streams.json > $ osc process -n yourproject -f eap/eap6-basic-sti.json -v APPLICATION_NAME=helloworld,APPLICATION_HOSTNAME=helloworld.yourproject.l... | osc create -n yourproject -f - > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20051) As a I user I want to be able to automatically install webhooks into my GitHub repository

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20051?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20051: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > As a I user I want to be able to automatically install webhooks into my GitHub repository > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20051 > URL: https://issues.jboss.org/browse/JBIDE-20051 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: new_and_noteworthy, openshift_v3 > Fix For: 4.5.0.Final > > Original Estimate: 4 days > Remaining Estimate: 4 days > > I want to be able to automatically install webhooks into my github repository from Eclipse. > We can detect if a project has a github url. > We can probably detect the user github credentials, or ask the user his credentials before trying to install the webhook. > There must be a GitHub API that allows to then add webhooks automatically. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 2017