-
Bug
-
Resolution: Done
-
Major
-
4.4.3.AM1
-
devex #129 March 2017
-
2
-
Workaround Exists
-
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:
The webconsole allows you to inspect those logs:
- relates to
-
JBIDE-23622 Build Log: impossible to get logs once the build pod is completed
- Closed