June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24445) OpenShift server adapter is not working, when rsync is not on path (Upstream issue)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24445?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24445: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > OpenShift server adapter is not working, when rsync is not on path (Upstream issue) > ----------------------------------------------------------------------------------- > > Key: JBIDE-24445 > URL: https://issues.jboss.org/browse/JBIDE-24445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.4.Final > Environment: Windows 10 > Reporter: Radim Hopp > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.Final > > > Using server adapter, when rsync is not on path results in errors like: > {noformat} > Could not sync C:\Users\jbossqa\rhopp\workspace-sidnfiweun\.metadata\.plugins\org.jboss.ide.eclipse.as.core\dfgdfg@eap-app\deploy to all pods running the service eap-app > OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Download cwRsync for Windows and add it to your PATH. > Ignoring the following flags because they only apply to rsync: --exclude > tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory > tar: ROOT.war/index.html: Cannot open: Not a directory > tar: ROOT.war/index.xhtml: Cannot open: Not a directory > tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory > tar: Exiting with failure status due to previous errors > error: error extracting tar at destination directory: command terminated with exit code 2 > {noformat} > More info in upstream issue: https://github.com/openshift/origin/issues/14075 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24174) When deploying user should be able to set the health checks (readiness and liveness)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24174?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24174: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > When deploying user should be able to set the health checks (readiness and liveness) > ------------------------------------------------------------------------------------ > > Key: JBIDE-24174 > URL: https://issues.jboss.org/browse/JBIDE-24174 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v2, wizard > Fix For: 4.5.0.Final > > > Note: this is not yet supported with the OCP web console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24175) Command to tune the health checks (readiness and liveness)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24175?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24175: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Command to tune the health checks (readiness and liveness) > ---------------------------------------------------------- > > Key: JBIDE-24175 > URL: https://issues.jboss.org/browse/JBIDE-24175 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > 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-24176) When deploying user should be able to tune storage

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24176?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24176: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > When deploying user should be able to tune storage > -------------------------------------------------- > > Key: JBIDE-24176 > URL: https://issues.jboss.org/browse/JBIDE-24176 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.5.0.Final > > > Note: this is not yet supported by OCP Web Console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[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.Final (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.Final > > 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)

8 years, 9 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.Final (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.Final > > > 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)

8 years, 9 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.Final (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: application_wizard, openshift, openshift_v3 > Fix For: 4.5.0.Final > > 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)

8 years, 9 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.Final (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.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24147) Pipeline view support

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24147?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24147: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Pipeline view support > --------------------- > > Key: JBIDE-24147 > URL: https://issues.jboss.org/browse/JBIDE-24147 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Jeff MAURY > Labels: openshift, openshift_v3 > 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-22810) OpenShift Explorer: empty at start

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22810: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Environment: windows > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: explorer, openshift_v3, windows > Fix For: 4.5.0.Final > > Attachments: EmptyViewAtStart.png > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- 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