[JBoss JIRA] (JBIDE-21578) CDK server should create openshift connection with no password set.
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21578?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21578:
------------------------------------
QE has decided they are comfortable w/ a respin & staging tonight w/ QE testing to start tomorrow. Now we just need [~akazakov] to approve including this in the Beta2 respin-a.
> CDK server should create openshift connection with no password set.
> --------------------------------------------------------------------
>
> Key: JBIDE-21578
> URL: https://issues.jboss.org/browse/JBIDE-21578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.3.1.Beta2, 4.3.1.CR1, 4.4.0.Alpha1
>
>
> The CDK server adapter should create an openshift server connection with only a username and with no password. If the underlying openshift requires one, openshift tools should prompt for it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21563) [regression] Explorer: Connection or (multiple) application deletion does not work anymore
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21563?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21563:
------------------------------------
QE has decided they are comfortable w/ a respin & staging tonight w/ QE testing to start tomorrow.
> [regression] Explorer: Connection or (multiple) application deletion does not work anymore
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-21563
> URL: https://issues.jboss.org/browse/JBIDE-21563
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: explorer, openshift_v2, respin-a
> Fix For: 4.3.1.Beta2, 4.3.1.CR1
>
>
> Previously it was possible to select multiple OpenShift 2 applications and delete them at once via context menu Delete application(s).... Currently there is no such context menu anymore and it is a pain to delete several applications one by one.
> Added by Slava: In my environment, Delete for objects of OpenShift 2 does not work at all (menu is shown, but nothing happens). It seems the cause is a slip in plugin.xml for Openshift 3, handler org.jboss.tools.openshift.internal.ui.handler.DeleteResourceHandler declared activeWhen with <or> (count==1 _or_ instanceof IResource). So, formally having a lot of restrictions but passing them, this handler imposes itself on all selections. Though, it is possible that the bug reveals not in all environments.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21559) Pod Log: should be able to select a container to show logs if pod contains more than 1 containers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21559?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21559:
-------------------------------------
Summary: Pod Log: should be able to select a container to show logs if pod contains more than 1 containers (was: Should can select a container to show logs when the pod contains more than 1 containers)
> Pod Log: should be able to select a container to show logs if pod contains more than 1 containers
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21559
> URL: https://issues.jboss.org/browse/JBIDE-21559
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: JBoss OpenShift 3 Tools: 3.1.0.Beta2-v20160122-0251-B156
> Reporter: Chunyun Chen
> Labels: openshift_v3, pod_log
> Fix For: 4.4.0.Alpha1
>
>
> The existing issue:
> 1.EXEC: Deploy a pod which contains more than 1 containers
> 2.EXEC: Expand the related service tree view in "OpenShift Explorer"
> 3.EXEC: Right click above pod -> click "Pod Log..."
> 4.ASSERT: Will meet some errors in "Console" window like "Error from server: a container name must be specified for pod logging-kibana-1-icxl2"
> So, we need find a method for user to specify a container to show logs when the pod has more than 1 containers.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21559) Pod Log: should be able to select a container to show logs if pod contains more than 1 containers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21559?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21559:
-------------------------------------
Labels: openshift_v3 pod_log (was: openshift_v3)
> Pod Log: should be able to select a container to show logs if pod contains more than 1 containers
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21559
> URL: https://issues.jboss.org/browse/JBIDE-21559
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: JBoss OpenShift 3 Tools: 3.1.0.Beta2-v20160122-0251-B156
> Reporter: Chunyun Chen
> Labels: openshift_v3, pod_log
> Fix For: 4.4.0.Alpha1
>
>
> The existing issue:
> 1.EXEC: Deploy a pod which contains more than 1 containers
> 2.EXEC: Expand the related service tree view in "OpenShift Explorer"
> 3.EXEC: Right click above pod -> click "Pod Log..."
> 4.ASSERT: Will meet some errors in "Console" window like "Error from server: a container name must be specified for pod logging-kibana-1-icxl2"
> So, we need find a method for user to specify a container to show logs when the pod has more than 1 containers.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21559) Pod Log: should be able to select a container to show logs if pod contains more than 1 containers
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21559?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21559:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
> Pod Log: should be able to select a container to show logs if pod contains more than 1 containers
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21559
> URL: https://issues.jboss.org/browse/JBIDE-21559
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: JBoss OpenShift 3 Tools: 3.1.0.Beta2-v20160122-0251-B156
> Reporter: Chunyun Chen
> Labels: openshift_v3, pod_log
> Fix For: 4.4.0.Alpha1
>
>
> The existing issue:
> 1.EXEC: Deploy a pod which contains more than 1 containers
> 2.EXEC: Expand the related service tree view in "OpenShift Explorer"
> 3.EXEC: Right click above pod -> click "Pod Log..."
> 4.ASSERT: Will meet some errors in "Console" window like "Error from server: a container name must be specified for pod logging-kibana-1-icxl2"
> So, we need find a method for user to specify a container to show logs when the pod has more than 1 containers.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3566:
----------------------------------
When I launch JBDS with -Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=https://dev.eclipse.org/recommenders/community/confess/v2/discovery
and attempt to recreate the steps above that Martin posted, I don't get any AERI dialog. And in Preferences > General > Error Reporting, I see the screenshot above for JBDS, not the fully-enabled one for JBT.
Suspect this might be because https://dev.eclipse.org/recommenders/community/confess/v2/discovery says:
{code} "acceptedProducts" : [ "org.eclipse.*" ],{code}
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Attachments: error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3566:
----------------------------------
We need to ensure that there's a valid property defined in JBDS, which can at least use -Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=https://dev.eclipse.org/recommenders/community/confess/v2/discovery
I suspect that default is not set in JBDS ootb.
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Attachments: error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3566) include AERI in JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3566 at 1/27/16 10:39 AM:
------------------------------------------------------------
So for this to work we need to ...
{quote}
look at https://wiki.eclipse.org/EPP/Logging#How_can_I_include_AERI_in_my_own_pro... for how to configure our own discovery site to look like https://dev.eclipse.org/recommenders/community/confess/v2/discovery
Maybe a URL like https://devstudio.redhat.com/9.0/aeri-discovery or http://download.jboss.org/jbosstools/mars/aeri-discovery ?
{quote}
Looking at https://dev.eclipse.org/recommenders/community/confess/v2/discovery I see we can specify which products/plugins/packages to report errors
Do we want to capture errors from org.eclipse.\* stuff, or just our own namespace: org.jboss.\*, org.hibernate.\*, com.jboss.\* ... ?
Reading through https://dev.eclipse.org/recommenders/community/confess/#/guide I see some great (um, not really) doc on how to configure the server to collect errors:
{quote}*Integrating Error Reporting into your own Eclipse RCP-based Products*
Attention: Please note that the error reporter does not yet have a public stable API. In case you want to use it within your product you should give us a heads-up on *recommenders-dev(a)eclipse.org*.
The URL where error reports are sent to can be configured via system properties (e.g. by specifying them in the eclipse.ini via ‑Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=http://your.server/url option).
However, further customizations (like whitelist modifications) may be required. Contact us on the mailing list for latest instructions. Patches that make the error reporter usable outside the Eclipse IDE setup are welcome.
{quote}
was (Author: nickboldt):
So for this to work we need to ...
{quote}
look at https://wiki.eclipse.org/EPP/Logging#How_can_I_include_AERI_in_my_own_pro... for how to configure our own discovery site to look like https://dev.eclipse.org/recommenders/community/confess/v2/discovery
Maybe a URL like https://devstudio.redhat.com/9.0/aeri-discovery or http://download.jboss.org/jbosstools/mars/aeri-discovery ?
{quote}
Looking at https://dev.eclipse.org/recommenders/community/confess/v2/discovery I see we can specify which products/plugins/packages to report errors
Do we want to capture errors from org.eclipse.* stuff, or just our own namespace: org.jboss.*, org.hibernate.*, com.jboss.* ... ?
Reading through https://dev.eclipse.org/recommenders/community/confess/#/guide I see some great (um, not really) doc on how to configure the server to collect errors:
{quote}*Integrating Error Reporting into your own Eclipse RCP-based Products*
Attention: Please note that the error reporter does not yet have a public stable API. In case you want to use it within your product you should give us a heads-up on *recommenders-dev(a)eclipse.org*.
The URL where error reports are sent to can be configured via system properties (e.g. by specifying them in the eclipse.ini via ‑Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=http://your.server/url option).
However, further customizations (like whitelist modifications) may be required. Contact us on the mailing list for latest instructions. Patches that make the error reporter usable outside the Eclipse IDE setup are welcome.
{quote}
> include AERI in JBDS
> --------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: build, target-platform
> Affects Versions: 9.1.0.Beta1, 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Attachments: error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months