December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23639) Application wizard: Templates parameters show wrong values if using existing eclipse project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23639?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23639: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > Application wizard: Templates parameters show wrong values if using existing eclipse project > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23639 > URL: https://issues.jboss.org/browse/JBIDE-23639 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Marián Labuda > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.AM1 > > > When creating a new OpenShift 3 application based on an eclipse project from workspace using a template, template parameters shows wrong values. E.g. I am having a project with git repo URL URL_A and template is based on source code from git repo URL URL_B. In the wizard, if I select at first template and then eclipse project, the template parameters values on the next wizard page shows values of the template instead of eclipse project. But correct values are shown. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[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.4.3.AM1 (was: 4.4.3.AM2) > 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.4.3.AM1 > > 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)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23463: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > Properties: Build pod has state of exit code 0 instead of correct status completed > ---------------------------------------------------------------------------------- > > Key: JBIDE-23463 > URL: https://issues.jboss.org/browse/JBIDE-23463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: exit-code-0.png > > > When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests. > steps: > # EXEC: create an application via a s2i template > # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view" > # EXEC: in Properties: select "Pods" tab. > # ASSERT: a build pod is appearing > # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods > Result: > The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise) > !exit-code-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23356) Deploy Docker Wizard: Image Stream created for local images is not shown in resource summary

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23356?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23356: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > Deploy Docker Wizard: Image Stream created for local images is not shown in resource summary > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23356 > URL: https://issues.jboss.org/browse/JBIDE-23356 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.3.AM1 > > > When deploying a local docker image to OpenShift and pushing it to OpenShift registry, ImageStream is also created but it is not listed in the table of Resource creation summary right after deployment. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21331) Connection wizard: it looks as if the wizard is creating new connection instances several times

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21331?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21331: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > Connection wizard: it looks as if the wizard is creating new connection instances several times > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-21331 > URL: https://issues.jboss.org/browse/JBIDE-21331 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.4.3.AM1 > > > The connection wizard creates new connection instances in several places which seems unnecessary (we need it at least once where we dont want to modify an existing connection and operate on a copy before merging the changes back upon successfull verification) > {code:title=ConnctionWizardPageModel} > private void initEditConnection(IConnection connection) { > this.selectedConnection = connection; > this.connection = connection.clone(); > ... > {code} > {code:title=ConnctionWizardPageModel} > public IStatus connect() { > ... > try { > this.connection = createConnection(); > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23622) Build Log: impossible to get logs once the build pod is completed

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23622?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23622: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > Build Log: impossible to get logs once the build pod is completed > ----------------------------------------------------------------- > > Key: JBIDE-23622 > URL: https://issues.jboss.org/browse/JBIDE-23622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Marián Labuda > Labels: build_log, openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: cannot-build-log.png, log_build.png > > > When I am trying to get a log of completed build, either via context menu of a pod in tabbed property Pods or via context menu of a build in tabbed property Builds, I get following error dialog > !log_build.png! > There is no error in log. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23006) OkHttp reports leaked connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23006?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23006: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > OkHttp reports leaked connections > --------------------------------- > > Key: JBIDE-23006 > URL: https://issues.jboss.org/browse/JBIDE-23006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Fix For: 4.4.3.AM1 > > > After connecting to an OpenShift instance, some warnings show up in the logs eventually: > {noformat} > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > {noformat} > I haven't figured out exactly what steps cause these yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22439: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM1 > > Attachments: sornarcube-github-signup-error.png > > Original Estimate: 2 days > Time Spent: 5 hours > Remaining Estimate: 1 day, 3 hours > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - Findbugs > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22362: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > Server Adapter: Static changes done to nodejs application are not visible > ------------------------------------------------------------------------- > > Key: JBIDE-22362 > URL: https://issues.jboss.org/browse/JBIDE-22362 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.3.AM1 > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating. > So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23026) Integration tests: improve test stability

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23026?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23026: ------------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > Integration tests: improve test stability > ----------------------------------------- > > Key: JBIDE-23026 > URL: https://issues.jboss.org/browse/JBIDE-23026 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: integration_tests > Fix For: 4.4.3.AM1 > > > There are several impediments to the test stability: > * tests dont set up their env individually > * some tests assert the oc binary, but this binary is not the same across platforms (oc, oc.exe, etc): org.jboss.tools.openshift.reddeer.requirement.OCBinary et org.jboss.tools.openshift.reddeer.utils.OpenShiftLabel -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 December 2016