April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24183) OpenShiftDebugUtilsTest: #testGetDebuggingContext is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24183?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24183: ------------------------------------------ merged into jbosstools-4.4.x and cherry-picked into master > OpenShiftDebugUtilsTest: #testGetDebuggingContext is failing > ------------------------------------------------------------ > > Key: JBIDE-24183 > URL: https://issues.jboss.org/browse/JBIDE-24183 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.4.AM3, 4.5.0.AM1 > > > {code} > testGetDebuggingContext(org.jboss.tools.openshift.test.core.server.OpenShiftDebugUtilsTest) Time elapsed: 0.018 sec <<< FAILURE! > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertFalse(Assert.java:64) > at org.junit.Assert.assertFalse(Assert.java:74) > at org.jboss.tools.openshift.test.core.server.OpenShiftDebugUtilsTest.testGetDebuggingContext(OpenShiftDebugUtilsTest.java:109) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22969: ------------------------------------- Sprint: devex #123 November 2016, devex #130 April 2017 (was: devex #123 November 2016, devex #129 March 2017) > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.AM2 > > Attachments: proxy_settings.png, proxy_settings_2.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23900) Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23900?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23900: ------------------------------------- Sprint: devex #130 April 2017 (was: devex #129 March 2017) > Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff > ---------------------------------------------------------------------------------- > > Key: JBIDE-23900 > URL: https://issues.jboss.org/browse/JBIDE-23900 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.AM2 > > > We should isolate EAP/Wildfly and NodeJS specific stuff for the server adapter into separate classes / extensions > We should also provide a mechanism for the sever adapter to be stack agnostic so that we can add more stacks by just addding an extension > This will be probably required by FUSE integration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23136: ------------------------------------- Sprint: devex #123 November 2016, devex #130 April 2017 (was: devex #123 November 2016, devex #129 March 2017) > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.4.AM2 > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4354) migrate Install Tests jobs to CCI

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4354?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4354: ----------------------------- Component/s: build > migrate Install Tests jobs to CCI > --------------------------------- > > Key: JBDS-4354 > URL: https://issues.jboss.org/browse/JBDS-4354 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.4.0.AM3 > > > Migrate jobs in http://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/I... to CCI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24223) CDK3 server adapter: errors on "service-manager" when starting it while cdk is already running

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24223?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24223: ------------------------------------- Summary: CDK3 server adapter: errors on "service-manager" when starting it while cdk is already running (was: CDK3 server adapter: errors on "service-manager" when starting while having started cdk3) > CDK3 server adapter: errors on "service-manager" when starting it while cdk is already running > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-24223 > URL: https://issues.jboss.org/browse/JBIDE-24223 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Attachments: image-2017-04-04-16-06-02-928.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 commented on JBIDE-24146: ------------------------------------------ Eclipse mylyn builds has a jenkins connector http://marketplace.eclipse.org/content/hudsonjenkins-mylyn-builds-connector But this connector doesnt support jenkins builds yet apparently, but they're working on it: https://bugs.eclipse.org/bugs/show_bug.cgi?id=510409 > 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 > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3, wizard > Fix For: 4.4.4.AM3 > > Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.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)

9 years

1
0
0 / 0

[JBoss JIRA] (ERT-389) TypeScript debugging [EBZ#487465]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-389?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-389: ---------------------------- Sprint: (was: devex #129 March 2017) > TypeScript debugging [EBZ#487465] > --------------------------------- > > Key: ERT-389 > URL: https://issues.jboss.org/browse/ERT-389 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: Debug, bzira > > I'm developping a TypeScript plugins based on JSDT & tsserver https://github.com/angelozerr/typescript.java and it should be very cool if JSDT debugger could debug TypeScript (by using source map). > If you are interested to work together about integration TypeScript (with JSDT), I have created an issue at https://github.com/angelozerr/typescript.java/issues/2. > Please note that TypEcs support debugging with Eclipse https://github.com/axmor/typecs/tree/master/src/com.axmor.eclipse.typescr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ERT-389) TypeScript debugging [EBZ#487465]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-389?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-389: ---------------------------- Story Points: 2 (was: 5) > TypeScript debugging [EBZ#487465] > --------------------------------- > > Key: ERT-389 > URL: https://issues.jboss.org/browse/ERT-389 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: Debug, bzira > > I'm developping a TypeScript plugins based on JSDT & tsserver https://github.com/angelozerr/typescript.java and it should be very cool if JSDT debugger could debug TypeScript (by using source map). > If you are interested to work together about integration TypeScript (with JSDT), I have created an issue at https://github.com/angelozerr/typescript.java/issues/2. > Please note that TypEcs support debugging with Eclipse https://github.com/axmor/typecs/tree/master/src/com.axmor.eclipse.typescr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ERT-465) Include plug-in jsdt.integration.tests into org.eclipse.wst.jsdt_tests.feature [EBZ#508353]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-465?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk commented on ERT-465: --------------------------------- Create small project for npm test + create CQ for this test project > Include plug-in jsdt.integration.tests into org.eclipse.wst.jsdt_tests.feature [EBZ#508353] > ------------------------------------------------------------------------------------------- > > Key: ERT-465 > URL: https://issues.jboss.org/browse/ERT-465 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > > We need to include plug-in jsdt.integration.tests into org.eclipse.wst.jsdt_tests.feature -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 2017