December 2016 - jbosstools-issues

[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.AM2 (was: 4.4.3.AM1) > 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.AM2 > > 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-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21593: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21593 > URL: https://issues.jboss.org/browse/JBIDE-21593 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: Fedora 22, GTK 3. > Reporter: Marián Labuda > Labels: application_wizard, explorer, openshift_v3 > Fix For: 4.4.3.AM2 > > Attachments: empty_project.png > > > When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot > !empty_project.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23589) Integration tests global refactoring: org.jboss.tools.openshift.ui.bot.test

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23589?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23589: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Integration tests global refactoring: org.jboss.tools.openshift.ui.bot.test > --------------------------------------------------------------------------- > > Key: JBIDE-23589 > URL: https://issues.jboss.org/browse/JBIDE-23589 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: integration, integration_tests, openshift > Fix For: 4.4.3.AM2 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.openshift.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23389) OpenShift 3.4 support

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23389?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23389: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > OpenShift 3.4 support > --------------------- > > Key: JBIDE-23389 > URL: https://issues.jboss.org/browse/JBIDE-23389 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.4.3.AM2 > > > OpenShift 3.4 is currently in progress but we need to start testing it now to see if we need adjust anything in our tools to support it. > cc: [~adietish] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23019) Integration tests: have them running automatically, continuously

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23019?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23019: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Integration tests: have them running automatically, continuously > ---------------------------------------------------------------- > > Key: JBIDE-23019 > URL: https://issues.jboss.org/browse/JBIDE-23019 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.3.AM2 > > > The integration tests suite is very lenghty to run and should thus be run in a continuous manner on our CI. > There are several pain-points currently: > - there's no dedicated OS instance to run them against > - tests are not stable > - etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22869: ------------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- 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.AM2 (was: 4.4.3.AM1) > 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.AM2 > > > 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] (JBDS-4112) create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4112?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4112. ------------------------------ Verified, script ide-config.priperties.py is able to detect not commented line containing ".GA" or ".Final". Unfortunatelly the link to jenkins job provided in description [1] is broken, so I can't check it and I tested the script only on my pc. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-4112 > URL: https://issues.jboss.org/browse/JBDS-4112 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.GA > > > As reported in https://developer.jboss.org/message/964029#964029 it seems there may have been a situation where a user installed devstudio 10.1.0.GA from the installer jar, but then using Central got the staging/snapshot URLs into their Available Update Sites, which then caused them to be prompted to update to 10.2. > Mixing an AM1 staging build into a .GA stable build should not happen. > We need a better test/check to ensure that if GA is live, its ide-config.properties content NEVER points to the future snapshot/staging content. > This testing could be part of the staging/release guide, but could also be run as a Jenkins job to check at intervals: > * ide-config.properties: URLs exist, are valid, don't 404, don't mismatch content > * foundation plugin / devstudio version plugin have correct version (eg., can't still be GA after GA is live) - see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... job -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23654) Remember last Project type, build system and stack used to create a new project using the forge tooling

by Aurélien Pupier (JIRA)

Aurélien Pupier created JBIDE-23654: --------------------------------------- Summary: Remember last Project type, build system and stack used to create a new project using the forge tooling Key: JBIDE-23654 URL: https://issues.jboss.org/browse/JBIDE-23654 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Affects Versions: 4.4.2.Final Reporter: Aurélien Pupier Attachments: image-2016-12-19-13-21-02-213.png When using the Forge tooling to create a new project, it would be nice to remember the last project type, build system and stack used on the first wizard page. !image-2016-12-19-13-21-02-213.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23475) split ide-config.properties into multiple files

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23475?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23475. -------------------------------- Ide-config.properties file has been splitted according to description of this jira. I tried to run build as Nick suggested and it works as expected. So closing this jira. > split ide-config.properties into multiple files > ------------------------------------------------- > > Key: JBIDE-23475 > URL: https://issues.jboss.org/browse/JBIDE-23475 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, central-update > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.Final > > > I'd like to split the contents of the current ide-config.properties file into multiple files so the content is easier to maintain via code generation. > So, rather than 1 big file [1] we could split this into 5 files: > * ide-config_4.4.snapshots.properties - contains the properties needed for jbosstools and devstudio CI builds (currently 4.4.2.Final and 10.2.0.GA) > * ide-config_4.4.staging.properties - contains the properties needed for the latest jbosstools and devstudio staging build (currently 4.4.2.AM3 and 10.2.0.AM3) > * ide-config_4.4.development.properties - contains the properties needed for the latest jbosstools and devstudio development build (currently 4.4.2.AM2 and 10.1.0.GA) > * ide-config_4.4.stable.properties - contains the properties needed for the latest jbosstools and devstudio stable build (currently 4.4.1.Final and 10.1.0.GA) > * ide-config.properties - contains all the other properties for 4.3.x and earlier releases > [1] https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... > By splitting this into smaller files, the contents that need to be changed every 3 weeks when we stage or release a build could be generated destructively, rather than having to worry about making changes w/ sed and not accidentally pushing in an invalid URL or value. > From the central side of things, we would just want to treat all ide-config*.properties files as if they were pieces of a single file, and load them all into the same hash of properties we currently have from the single file. -- 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