[jbosstools-issues] [JBoss JIRA] (JBIDE-20099) enable a logstream for Openshift Pods
Andre Dietisheim (JIRA)
issues at jboss.org
Wed Jun 24 10:47:02 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-20099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083342#comment-13083342 ]
Andre Dietisheim edited comment on JBIDE-20099 at 6/24/15 10:46 AM:
--------------------------------------------------------------------
setting 4.3.0.Beta2 as fixVersion for now since I would think that this is most likely even more important than proper port forwarding?
In my thinking we were framed by the approach in v2 where port forwarding and inspecting the log were both relying on ssh. This made us think that by having port forwarding we'd have the infrastructure to tail log files. Here in v3 we have a similar situation where both apparently rely on SPDY which we'll provide via wrapping the cli we'd have the basics to be able to inspect the logs. Thinking twice I would think that inspecting the logs is more important than port forwarding per se.
[~maxandersen] [~jcantrill] WDYT?
was (Author: adietish):
setting 4.3.0.Beta2 as fixVersion for now since I would think that this is most likely even more important than proper port forwarding?
[~maxandersen] WDYT?
> enable a logstream for Openshift Pods
> -------------------------------------
>
> Key: JBIDE-20099
> URL: https://issues.jboss.org/browse/JBIDE-20099
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Diógenes Rettori
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta2
>
>
> enable the eclipse console to show
> oc get logs <pod>
> oc get build-logs <build>
> You click on the pod, then right-click show logs, or double click go to logs...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jbosstools-issues
mailing list