]
Andre Dietisheim updated JBIDE-23708:
-------------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
Pod Log: unable to get build log if build failed with error
-----------------------------------------------------------
Key: JBIDE-23708
URL:
https://issues.jboss.org/browse/JBIDE-23708
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.3.AM1
Reporter: Andre Dietisheim
Labels: logs, properties
Fix For: 4.4.3.Final
Attachments: cannot-get-logs-for-erroring-build.png,
webconsole-logs-for-erroring-build.png
steps to reproduce:
# ASSERT: make sure that you have a build that failed (ex. launch a nodejs build and shut
down your vpn. The build will fail because it cannot connect to the registry)
# EXEC: in Properties view: select "Builds" tab and choose your erroring build.
Choose "Build Log..." in it's context menu
Result:
You're told that you cannot get the logs for an erroring build. You therefore cannot
have insights on why your build failed:
!cannot-get-logs-for-erroring-build.png!
The webconsole allows you to inspect those logs:
!webconsole-logs-for-erroring-build.png!