April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24345) Create New and Noteworthy for 4.4.4.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24345?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24345: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Create New and Noteworthy for 4.4.4.Final > ----------------------------------------- > > Key: JBIDE-24345 > URL: https://issues.jboss.org/browse/JBIDE-24345 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.4.4.Final > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23623: ------------------------------- Sprint: devex #127 February 2017, devex #128 February 2017 (was: devex #127 February 2017, devex #128 February 2017, devex #131 May 2017 (JBIDE)) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > Attachments: jira.txt, prepare-am1.txt, run.04262017.log, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24241) Server adapter not working when created from replication controller fallback

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24241?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24241: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Server adapter not working when created from replication controller fallback > ---------------------------------------------------------------------------- > > Key: JBIDE-24241 > URL: https://issues.jboss.org/browse/JBIDE-24241 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Jan Richter > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.4.4.Final > > > When no service nor deployment config is available, it is possible to create a server adapter using replication controllers. A server adapter created this way errors on start with the following message: > {noformat} > An internal error occurred during: "Starting nodejs-1 (ReplicationController) at OpenShift 3 (192.168.42.24)". > deploymentconfigs "nodejs" not found deploymentconfigs "nodejs" not found > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24217) Deployment config is not shown in OpenshiftExplorer, when service is deleted.

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24217?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24217: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Deployment config is not shown in OpenshiftExplorer, when service is deleted. > ----------------------------------------------------------------------------- > > Key: JBIDE-24217 > URL: https://issues.jboss.org/browse/JBIDE-24217 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM2 > Reporter: Radim Hopp > Assignee: Jeff MAURY > Fix For: 4.4.4.Final > > > When service is deleted (in Openshift Explorer), the whole tree node is removed (even though other resources still exist in openshift). > The Deployment config node is not even shown when "refresh" is used. Only thing that helps is removing whole Openshift connection and adding it back again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24307) Filter out Build config which have no git url configured in "Import OpenShift Application" dialog

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24307?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24307: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Filter out Build config which have no git url configured in "Import OpenShift Application" dialog > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-24307 > URL: https://issues.jboss.org/browse/JBIDE-24307 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: import_wizard, openshift_v3 > Fix For: 4.4.4.Final, 4.5.0.AM1 > > Attachments: image-2017-04-25-15-22-03-598.png, image-2017-04-25-15-22-12-510.png > > > it will avoid to have an error dialog just after > !image-2017-04-25-15-22-12-510.png|thumbnail! > Even more that thsi information is already retrieved to be displayed in "Build config details" > !image-2017-04-25-15-22-03-598.png|thumbnail! > Anothe rpossibility is to greyet out them with a tooltip explaining why we can't select them > and/or disabled Next:Finish buttons -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24318) Analyze watch replacement

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24318?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24318: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Analyze watch replacement > ------------------------- > > Key: JBIDE-24318 > URL: https://issues.jboss.org/browse/JBIDE-24318 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: openshift, openshift_v3 > > Analyze how the watch and watch manager can be implemented when switching to the fabric8 client -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24308) Disable "Import application" contextual menu on build config having no git url configured

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24308?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24308: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Disable "Import application" contextual menu on build config having no git url configured > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24308 > URL: https://issues.jboss.org/browse/JBIDE-24308 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: import_wizard, openshift_v3 > Fix For: 4.4.4.Final, 4.5.0.AM1 > > Attachments: image-2017-04-25-15-25-07-634.png, image-2017-04-25-15-25-34-373.png > > > !image-2017-04-25-15-25-07-634.png|thumbnail! > it avoids to have an error dialog just after: > !image-2017-04-25-15-25-34-373.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23882) Automate test of installation of software from Red Hat Central into devstudio RPM

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23882?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23882: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Automate test of installation of software from Red Hat Central into devstudio RPM > --------------------------------------------------------------------------------- > > Key: JBIDE-23882 > URL: https://issues.jboss.org/browse/JBIDE-23882 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Environment: RHEL7, devstudio RPM > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.4.4.Final > > > We need to catch problems like in JBDS-4263. > [~lvalach] said: {quote} > I think I should automate test of installation from Central, because this procedure is quite time consuming. > {quote} > [~nickboldt] said: {quote} > before you do that might want to look at the existing automated tests we have: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g.... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-p.... > of course those are not based on rpm installs, but on eclipse platform binary or JEE packages. We could try modifying both p2director (headless) and install-grinder (head w/ swt) scripts to support doing an rpm install too... not sure how since that would require running as root > maybe you could just use the scripts to automate the process of doing the installs AFTER you have rpm installed locally > so ... partial automation > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4295) Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4295?page=com.atlassian.jira.plugin.... ] Jeff MAURY updated JBDS-4295: ----------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Create smoke test that installs Devstudio RPM and then all the Central/EarlyAccess stuff on top > ----------------------------------------------------------------------------------------------- > > Key: JBDS-4295 > URL: https://issues.jboss.org/browse/JBDS-4295 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: integration-tests, rpm > Affects Versions: 10.4.0.AM1 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.4.0.GA > > > We need to create jenkins job which can be used as smoke test for Devstudio installed from RPM on RHEL7 via the RHSCL yum repo [1] & the devstudio yum repo [2]. This job should be configurable, we want to be able to pass in a different parameters as URLs and then use the same job to test both snapshot and staging. > The job should: > # Install rh-eclipse46-devstudio > # Clean and start eclipse in strict mode and in clean work space > # Install all stuff from Red Hat Central *using graphical interface* > ** Install everything at once - this is the fastest approach but also makes diagnosing errors more difficult. > ** So, when problems occur, could re-run the job (manually or with naginator plugin?) using parameter connectorIDsToInstall = "net.sourceforge.pmd.eclipse" [3] for example > # Restart Eclipse > # Check for errors > # Should also test if some software from Central works - run quickstarts or wizards > Possible configuration parameters: > * RPM URL (snapshot/staging/stable) [2] > * RHSCL URL[1] > * jboss.discovery.directory.url, jboss.discovery.site.integration-stack.url or something similar (eg., https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e... or https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1... or https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/) > * ERROR_PATTERN (like [rpm_rh_central_test|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.red...] has) > * TESTS_FORK = jbosstools ? > * TEST_BRANCH = master or jbosstools-4.4.x or jbosstools-4.4.4.x ? > * connectorIDsToInstall = "" (install everything found) or specific value [3] for re-running if something fails > [1] http://download.devel.redhat.com/rel-eng/latest-RHSCL-2-RHEL-7/compose/Se... or similar > [2] https://devstudio.jboss.com/static/10.0/stable/rpms/x86_64/ or https://devstudio.jboss.com/10.0/staging/builds/devstudio-10.3.0.GA-build... or https://devstudio.jboss.com/10.0/snapshots/rpms/10.4.0/x86_64/ > [3] https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24312: ------------------------------- Sprint: devex #131 April 2017 (was: devex #131 May 2017 (JBIDE)) > Explorer: SSL certificate dialog shows up many many times when using internal test server > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24312 > URL: https://issues.jboss.org/browse/JBIDE-24312 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Environment: MacOS > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.4.4.Final > > Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 April 2017