May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21869) Encoding issue in when streaming Build Logs to the console

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21869?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21869: --------------------------------------- [~mlabuda] how does this compare to the output of 'oc log' > Encoding issue in when streaming Build Logs to the console > ---------------------------------------------------------- > > Key: JBIDE-21869 > URL: https://issues.jboss.org/browse/JBIDE-21869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: screenshot-1.png, screenshot-2.png > > > Create a new nodejs app, when a build is running, in the OpenShift Explorer, right click on the build and select the Build Log... menu. > It'll start to spew weird characters eventually : > {noformat} > I0315 10:38:28.749220 1 docker.go:286] Image "registry.access.redhat.com/openshift3/nodejs-010-rhel7:latest" not available locally, pulling ... > I0315 10:39:16.195418 1 source.go:197] Downloading "https://github.com/openshift/nodejs-ex.git" ... > I0315 10:39:19.670243 1 install.go:236] Using "assemble" installed from "image:///usr/libexec/s2i/assemble" > I0315 10:39:19.670318 1 install.go:236] Using "run" installed from "image:///usr/libexec/s2i/run" > I0315 10:39:19.670356 1 install.go:236] Using "save-artifacts" installed from "image:///usr/libexec/s2i/save-artifacts" > ---> Installing application source > ---> Building your Node application from source > E0315 10:39:21.193046 1 util.go:91] npm info it worked if it ends with ok > E0315 10:39:21.193216 1 util.go:91] npm info using npm(a)2.14.13 > E0315 10:39:21.193229 1 util.go:91] npm info using node(a)v0.10.40 > ... > E0315 10:39:27.511826 1 util.go:91] npm info prepublish nodejs-ex(a)0.0.1 > ejs(a)2.4.1 node_modules/ejs > express(a)4.13.4 node_modules/express > �� escape-html(a)1.0.3 > �� array-flatten(a)1.1.1 > �� utils-merge(a)1.0.0 > �� cookie-signature(a)1.0.6 > �� merge-descriptors(a)1.0.1 > �� fresh(a)0.3.0 > �� methods(a)1.1.2 > �� range-parser(a)1.0.3 > �� vary(a)1.0.1 > �� path-to-regexp(a)0.1.7 > �� cookie(a)0.1.5 > �� parseurl(a)1.3.1 > �� content-type(a)1.0.1 > �� etag(a)1.7.0 > �� content-disposition(a)0.5.1 > �� serve-static(a)1.10.2 > �� depd(a)1.1.0 > �� qs(a)4.0.0 > �� finalhandler(a)0.4.1 (unpipe(a)1.0.0) > �� on-finished(a)2.3.0 (ee-first(a)1.1.1) > �� debug(a)2.2.0 (ms(a)0.7.1) > �� proxy-addr(a)1.0.10 (forwarded(a)0.1.0, ipaddr.js(a)1.0.5) > �� send(a)0.13.1 (destroy(a)1.0.4, statuses(a)1.2.1, ms(a)0.7.1, mime(a)1.3.4, http-errors(a)1.3.1) > �� type-is(a)1.6.12 (media-typer(a)0.3.0, mime-types(a)2.1.10) > �� accepts(a)1.2.13 (negotiator(a)0.5.3, mime-types(a)2.1.10) > mongodb(a)2.1.8 node_modules/mongodb > �� es6-promise(a)3.0.2 > �� mongodb-core(a)1.3.5 (bson(a)0.4.22, require_optional(a)1.0.0) > �� readable-stream(a)1.0.31 (inherits(a)2.0.1, isarray(a)0.0.1, string_decoder(a)0.10.31, core-util-is(a)1.0.2) > E0315 10:39:27.684535 1 util.go:91] npm info ok > I0315 10:39:42.202321 1 sti.go:245] Using provided push secret for pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image > I0315 10:39:42.202361 1 sti.go:249] Pushing 172.30.183.94:5000/node/nodejs-mongodb-example:latest image ... > {noformat} > I'm running on OSX -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22239: -------------------------------- Sprint: devex #114 May 2017 > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.4.0.Alpha2 > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-527) com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-527?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-527. ----------------------------------- Verified with JBDS-IS 9.0.0.GA-v20160503-1832-B2 > com.jboss.devstudio.integration-stack.*.feature versions don't have qualifier, just a timestamp > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-527 > URL: https://issues.jboss.org/browse/JBTIS-527 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Minor > Fix For: 9.0.0.GA > > > Looking in https://devstudio.redhat.com/9.0/stable/updates/integration-stack/9.0.0.A... I see these 4 IUs: > {code} > com.jboss.devstudio.integration-stack.bpr.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.ds.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.fuse.feature.feature.jar 9.0.0.201510070121 > com.jboss.devstudio.integration-stack.soa.feature.feature.jar 9.0.0.201510070121 > {code} > They should be versioned like everything else in JBT/JBDS/IS, using a full qualifier like: > * 9.0.0.Alpha2-v20151006-2058-B148 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22291) Deploy Docker Wizard: Add connection info

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22291?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22291: -------------------------------- Sprint: devex #114 May 2017 > Deploy Docker Wizard: Add connection info > ----------------------------------------- > > Key: JBIDE-22291 > URL: https://issues.jboss.org/browse/JBIDE-22291 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > When deploying from a context menu of a docker image from Docker Explorer and an OpenShift 3 connection/project is preselected, wizard use this connection and allow to set a specific project for deployment. Problem is that I don't see a connection where I am deploying. It is nice to know that it is selected connection/project from OpenShift explorer but it would be nice to have a combo box with preselected connection there or connection info in some way to be fully aware of what I am doing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-688) Rebuild JBDS-IS build to include new Drools/jBPM plugin

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-688?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-688. ----------------------------------- Verified with JBDS-IS 9.0.0.GA-v20160503-1832-B2 > Rebuild JBDS-IS build to include new Drools/jBPM plugin > ------------------------------------------------------- > > Key: JBTIS-688 > URL: https://issues.jboss.org/browse/JBTIS-688 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.0.GA > > > Currently, there is Drools 6.4.0.Final. But Bob and Kris want to include some bug fixes (see JBTIS-686) and ask for including the version 6.4.1.Final. > QE is now verifying the bug fixes and found some issues. Here we will discuss whether we include version 6.4.1.Final into JBDS-IS 9.0.0.GA or not. > Note that we cannot include Drools 6.3.1.Final since this version wasn't tested with JBDS 9.1.0.GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21720) Server Adapter: user choose default route when creating the server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21720?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21720: ----------------------------------- Assignee: Viacheslav Kabanovich (was: Andre Dietisheim) > Server Adapter: user choose default route when creating the server > ------------------------------------------------------------------ > > Key: JBIDE-21720 > URL: https://issues.jboss.org/browse/JBIDE-21720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.0.Alpha2 > > > Currently the Show in Web Browser always asks the user which route to open, which tends to be annoying when using the menu several times. For LiveReload support, it's even worse, the 1st route is always selected, which always leads to some problems when several routes are available. > I believe it would be best to let the user select the server adapter' default route in the OpenShift 3 Server wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22294) Build Configuration: Git Source section is cropped on OSX

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22294?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22294: ------------------------------------- yes. We have no wiggle room left on this page now. > Build Configuration: Git Source section is cropped on OSX > --------------------------------------------------------- > > Key: JBIDE-22294 > URL: https://issues.jboss.org/browse/JBIDE-22294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha2 > > > After creating a new openshift application, selecting a builder image, then on the next page: > !http://content.screencast.com/users/fbricon/folders/Jing/media/5e21b5d7-9cb1-43cf-bfe9-05c1ef6e0dad/00000404.png|width=800! > Context directory field / label are cropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22248) Some CI jobs fail at deploying to Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22248?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22248: ---------------------------------------- I don't know, I only saw things working since last Friday or so. It may be your fix. > Some CI jobs fail at deploying to Nexus > --------------------------------------- > > Key: JBIDE-22248 > URL: https://issues.jboss.org/browse/JBIDE-22248 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Nick, can you take a look why mvn deploy fails here? > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > It worked for us in the past. > It says: > {code} > [WARNING] Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 04:49 min > [INFO] Finished at: 2016-04-26T09:42:02-04:00 > [INFO] Final Memory: 19M/612M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > {code} > I'm not exactly sure how this works. Or is this something that is managed in jenkins config, so should I raise this with the jenkins team? > Cc: [~rawagner] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3877) can't import bigger maven/git project to jbds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3877?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3877: ----------------------------- Fix Version/s: 10.x > can't import bigger maven/git project to jbds > --------------------------------------------- > > Key: JBDS-3877 > URL: https://issues.jboss.org/browse/JBDS-3877 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: maven > Affects Versions: 9.1.0.GA > Reporter: Josef Ludvicek > Assignee: Viacheslav Kabanovich > Fix For: 10.x > > Attachments: jbds-import-camel-stuck.png, jbds-import-camel1.png > > > JBDS can't import sources of Apache Camel (maven project) > https://github.com/apache/camel > Steps to reproduce: > Clone it's git repo > {code} > git clone git@github.com:apache/camel.git > {code} > In jbds File -> Import Existing maven project > Unselect "resolve workspace projects" > Watch all CPU cores load on 100 % (tested on lenovo T440s / Intel i7 / Fedora 23) > Wait for error message (~20 minutes) > {code} > An internal error occurred during: "Importing Maven projects". > Java heap space > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3877) can't import bigger maven/git project to jbds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3877?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3877: ---------------------------------- Please attach anything recorded in your .log file or the Error Log view which might show what's happening. You could also try adding more Java heap space: https://wiki.eclipse.org/FAQ_How_do_I_increase_the_heap_size_available_to... Note that for a devstudio install, your eclipse.ini file is renamed to jbdevstudio.ini and is located in the studio/ folder. > can't import bigger maven/git project to jbds > --------------------------------------------- > > Key: JBDS-3877 > URL: https://issues.jboss.org/browse/JBDS-3877 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Bug > Components: maven > Affects Versions: 9.1.0.GA > Reporter: Josef Ludvicek > Assignee: Viacheslav Kabanovich > Attachments: jbds-import-camel-stuck.png, jbds-import-camel1.png > > > JBDS can't import sources of Apache Camel (maven project) > https://github.com/apache/camel > Steps to reproduce: > Clone it's git repo > {code} > git clone git@github.com:apache/camel.git > {code} > In jbds File -> Import Existing maven project > Unselect "resolve workspace projects" > Watch all CPU cores load on 100 % (tested on lenovo T440s / Intel i7 / Fedora 23) > Wait for error message (~20 minutes) > {code} > An internal error occurred during: "Importing Maven projects". > Java heap space > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016