[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:
-------------------------------------
Attachment: cannot-build-log.png
> 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, 4 months
[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:
-------------------------------------
Labels: build_log openshift_v3 (was: openshift_v3)
> 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: 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, 4 months
[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 commented on JBIDE-23622:
------------------------------------------
[~mlabuda] To me your initial bug request was nothing unexpected. Once cannot get logs from a pod that is completed. But then what's missing for me - and I believe that this was your completely valid point - is the ability to get the build logs for a build, even if the build is finished. I thus changed your initial issue description. Agree?
> 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: openshift_v3
> Fix For: 4.4.3.AM1
>
> Attachments: 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, 4 months
[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:
-------------------------------------
Steps to Reproduce:
EXEC: Create a new OpenShift 3 application from a template/builder image.
ASSERT: Build is triggered and visible in Properties view
EXEC: Wait until build is finished, in "Properties"/"Build" tab you can see your build in state "Competed"
EXEC: In "Properties" view, select "Builds" tab and pick "Build Log..."
Result:
You cannot get the log of the finished build, you're told that the pod for the build is Completed.
!cannot-build-log.png!
Excepted result:
You should be able to get the build logs even once they're finished. In oc you can do this via
(you list the build configs that exist and pick the one that is/was responsible for your build and use it to "oc logs")
{code}
oc logs -f bc/<build-config for your build>
{code}
was:
EXEC: Create a new OpenShift 3 application from a template/builder image.
ASSERT: Build is triggered and visible in Properties view
EXEC: Wait until build is finished, in "Properties"/"Build" tab you can see your build in state "Competed"
EXEC: In "Properties" view, select "Builds" tab and pick "Build Log..."
Result:
You cannot get the log of the finished build, you're told that the pod for the build is Completed.
!cannot-build-log.png!
Excepted result:
You should be able to get the build logs even once they're finished. In oc you can do this
> 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: openshift_v3
> Attachments: 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, 4 months
[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:
-------------------------------------
Steps to Reproduce:
EXEC: Create a new OpenShift 3 application from a template/builder image.
ASSERT: Build is triggered and visible in Properties view
EXEC: Wait until build is finished, in "Properties"/"Build" tab you can see your build in state "Competed"
EXEC: In "Properties" view, select "Builds" tab and pick "Build Log..."
Result:
You cannot get the log of the finished build, you're told that the pod for the build is Completed.
!cannot-build-log.png!
Excepted result:
You should be able to get the build logs even once they're finished. In oc you can do this
was:
EXEC: Create a new OpenShift 3 application from a template/builder image.
EXEC: Wait until build of an application finish.
ASSERT: There is a build pod with COMPLETE state.
EXEC: Select Pod Log... if opening via context menu of a pod, or Build Log... if opening via context menu of a build.
RESULT: Error dialog is shown.
EXPECTED RESULT: Log of completed build is shown in console.
> 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: openshift_v3
> Attachments: 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, 4 months
[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:
-------------------------------------
Summary: Build Log: impossible to get logs once the build pod is completed (was: Cannot get log of completed build pod)
> 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: openshift_v3
> Attachments: 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, 4 months
[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier commented on JBDS-4105:
---------------------------------------
[~chirino] Do we have already some maven goal/phase that can be used to produced the Source to be deployed?
What is the time required to generate it? it is to know if we can imagine it on Incremental build on on a full build only.
[~jeffmaury] [~rob.stryker] apart from the service/pod issue, how Eclipse OpenShift Tooling knows which folder/files it needs to redeploy using the s2i binary way? (it is using the s2i binary right?)
And by writing this question, i realize that we have the service/pod fix as requirements so we might be forced to provide just an "ignore" m2e connector for this plugin for the first release? the implication that I see is no leverage of the Eclipse OpenShift Tooling:
- will require manual rebuild
- no hot-deploy
- what else?
> Provide m2e connector for io.fabric8:fabric8-maven-plugin
> ---------------------------------------------------------
>
> Key: JBDS-4105
> URL: https://issues.jboss.org/browse/JBDS-4105
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: maven
> Reporter: Aurélien Pupier
>
> iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months