June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23602) Server adapter: Hot code replace failed dialog has poor usability

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23602?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23602: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Server adapter: Hot code replace failed dialog has poor usability > ----------------------------------------------------------------- > > Key: JBIDE-23602 > URL: https://issues.jboss.org/browse/JBIDE-23602 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM2 > > Attachments: hot-code-replace-failed-2.png > > > steps to reproduce: > # ASSERT: have jboss-helloworld running in OpenShift (create it via eap64-basic-s2i template), the source code for it imported to a workspace project and a server adapter for it > # EXEC: open HelloService and change it to the following: > {code:title=HelloService} > public class HelloService { > private static final String MAGIC_STRING = "42"; > > String createHelloMessage(String name) { > return "Hello " + name + ", the magic string is " + MAGIC_STRING + "!"; > } > } > {code} > and save the editor > Result: > "Hot code replace failed" dialog pops up, which is expected. > !hot-code-replace-failed-2.png! > But it's usability is poor: > * the affected module is not fully shown (half of it cut off) > * there's no margin on the right border of the dialog > * No button is pre-selected so that I can simply hit Return to pick a sane default choice (I have to hit tap to get to the button I want to press or use my mouse). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23513) OpenShift Explorer: Projects created outside of eclipse are not watched

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23513?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23513: ------------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.AM1) > OpenShift Explorer: Projects created outside of eclipse are not watched > ----------------------------------------------------------------------- > > Key: JBIDE-23513 > URL: https://issues.jboss.org/browse/JBIDE-23513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Rob Stryker > Assignee: Dmitrii Bocharov > Labels: explorer, openshift_v3 > Fix For: 4.5.x > > > See https://issues.jboss.org/browse/JBIDE-23184 for info -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23771) Pushing Image into Openshift registry fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23771?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23771: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Pushing Image into Openshift registry fails > ------------------------------------------- > > Key: JBIDE-23771 > URL: https://issues.jboss.org/browse/JBIDE-23771 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Environment: oc version > oc v1.3.2 > kubernetes v1.3.0+52492b4 > features: Basic-Auth GSSAPI Kerberos SPNEGO > Server https://openshift.hughestech.co:8443 > openshift v1.3.2 > kubernetes v1.3.0+52492b4 > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM2 > > Attachments: FailedPush.png > > > See the issue created in upstream: https://github.com/openshift/origin/issues/12603 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.5.0.AM2 > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24146) Support pipeline deployment style

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24146?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24146: ------------------------------------- Labels: application_wizard openshift openshift_v3 (was: openshift openshift_v3 wizard) > Support pipeline deployment style > --------------------------------- > > Key: JBIDE-24146 > URL: https://issues.jboss.org/browse/JBIDE-24146 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: application_wizard, openshift, openshift_v3 > Fix For: 4.5.0.AM2 > > Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.png, webui-edit-pipeline-file.png > > > In the web-console jenkins pipelines are supported in the following way: > * when opening up an empty project you get a special template: > !jenkins-pipeline-template.png! > * which offers 2 different jenkins variants (and a full example that contains app source and build pipeline): > !jenkins-variants.png! > * once executed you get a special build type *pipeline* > !pipeline-build.png! > * the full example template is using the following build config with the strategy type *JenkinsPipeline*: > {code} > apiVersion: v1 > kind: BuildConfig > metadata: > name: sample-pipeline > namespace: gulu > selfLink: /oapi/v1/namespaces/gulu/buildconfigs/sample-pipeline > uid: 12dec3c8-1948-11e7-a217-0251082287a6 > resourceVersion: '3757' > creationTimestamp: '2017-04-04T15:05:00Z' > labels: > app: jenkins-pipeline-example > name: sample-pipeline > template: application-template-sample-pipeline > annotations: > pipeline.alpha.openshift.io/uses: >- > [{"name": "nodejs-mongodb-example", "namespace": "", "kind": > "DeploymentConfig"}] > spec: > triggers: > - type: GitHub > github: > secret: secret101 > - type: Generic > generic: > secret: secret101 > runPolicy: Serial > source: > type: None > strategy: > type: JenkinsPipeline > jenkinsPipelineStrategy: > jenkinsfile: >- > node('nodejs') { > stage 'build' > openshiftBuild(buildConfig: 'nodejs-mongodb-example', showBuildLogs: > 'true') > stage 'deploy' > openshiftDeploy(deploymentConfig: 'nodejs-mongodb-example') > } > output: {} > resources: {} > postCommit: {} > nodeSelector: null > status: > lastVersion: 1 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 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: ------------------------------------- Labels: openshift_v3 server_adapter (was: openshift server_adapter) > 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.AM1 > > > We should provide suppport for Vert.x stack in OpenShift tooling -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 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: ------------------------------------- Labels: openshift_v3 server_adapter (was: openshift) > 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.AM1 > > > 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)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24146) Support pipeline deployment style

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24146?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24146: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Support pipeline deployment style > --------------------------------- > > Key: JBIDE-24146 > URL: https://issues.jboss.org/browse/JBIDE-24146 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3, wizard > Fix For: 4.5.0.AM2 > > Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.png, webui-edit-pipeline-file.png > > > In the web-console jenkins pipelines are supported in the following way: > * when opening up an empty project you get a special template: > !jenkins-pipeline-template.png! > * which offers 2 different jenkins variants (and a full example that contains app source and build pipeline): > !jenkins-variants.png! > * once executed you get a special build type *pipeline* > !pipeline-build.png! > * the full example template is using the following build config with the strategy type *JenkinsPipeline*: > {code} > apiVersion: v1 > kind: BuildConfig > metadata: > name: sample-pipeline > namespace: gulu > selfLink: /oapi/v1/namespaces/gulu/buildconfigs/sample-pipeline > uid: 12dec3c8-1948-11e7-a217-0251082287a6 > resourceVersion: '3757' > creationTimestamp: '2017-04-04T15:05:00Z' > labels: > app: jenkins-pipeline-example > name: sample-pipeline > template: application-template-sample-pipeline > annotations: > pipeline.alpha.openshift.io/uses: >- > [{"name": "nodejs-mongodb-example", "namespace": "", "kind": > "DeploymentConfig"}] > spec: > triggers: > - type: GitHub > github: > secret: secret101 > - type: Generic > generic: > secret: secret101 > runPolicy: Serial > source: > type: None > strategy: > type: JenkinsPipeline > jenkinsPipelineStrategy: > jenkinsfile: >- > node('nodejs') { > stage 'build' > openshiftBuild(buildConfig: 'nodejs-mongodb-example', showBuildLogs: > 'true') > stage 'deploy' > openshiftDeploy(deploymentConfig: 'nodejs-mongodb-example') > } > output: {} > resources: {} > postCommit: {} > nodeSelector: null > status: > lastVersion: 1 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24144) When deploying user should be able to tune the memory requirements

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24144?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24144: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > When deploying user should be able to tune the memory requirements > ------------------------------------------------------------------ > > Key: JBIDE-24144 > URL: https://issues.jboss.org/browse/JBIDE-24144 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, wizard > Fix For: 4.5.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24143) Fill the gap with the OpenShift console features

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24143?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24143: ------------------------------------- Fix Version/s: 4.5.0.AM2 (was: 4.5.0.AM1) > Fill the gap with the OpenShift console features > ------------------------------------------------ > > Key: JBIDE-24143 > URL: https://issues.jboss.org/browse/JBIDE-24143 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Jeff MAURY > Labels: openshift_v3 > Fix For: 4.5.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2017