January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23708: ------------------------------------- Description: 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! was: steps to reproduce: # ASSERT: make sure that you have a build that failed # 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! > 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 > 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! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21681) Truncated lines seen on openshift login page

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21681?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-21681. ------------------------------- Closing as dupe. > Truncated lines seen on openshift login page > -------------------------------------------- > > Key: JBIDE-21681 > URL: https://issues.jboss.org/browse/JBIDE-21681 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: OpenShift 3 Tools: 3.1.0.CR1-v20160212-1935-B177 > OS: Fedora 17 & 22 > Reporter: Xia Zhao > Assignee: Andre Dietisheim > Priority: Minor > Labels: login_wizard, openshift_v3 > Fix For: 4.4.3.AM1 > > Attachments: Screenshot from 2016-02-15 10-21-30.png > > > On the latest openshift login wizard inside JBT, the checkbox in the last line about whether you want to save credential is truncated. Please refer to the attached screenshot. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23315) Connection wizard: "Advanced >>" Button is cropped

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23315?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23315. ------------------------------- All looks well in 4.4.3.AM1 staged build, closing. > Connection wizard: "Advanced >>" Button is cropped > -------------------------------------------------- > > Key: JBIDE-23315 > URL: https://issues.jboss.org/browse/JBIDE-23315 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.3.AM1 > > Attachments: 2016-11-23 at 15-04-44.mp4, screenshot-1.png > > > Use case that reproduces in my environment (Ubuntu + GTK3): > 1. Ensure that OpenShift 3 connection is the recent one, by editing it. > 2. From main Eclipse menu call File->New->New OpenShift Application. > Wizard should open on Sign-In page with recent OpenShift 3 connection. > Without PR 'Advanced' button is cropped, with PR it is fully visible. > Second use case is: > 1. Ensure that OpenShift 3 connection is the recent one, by editing it in OpenShift Explorer. > 2. In Servers view call 'New->Server->OpenShift 3 Server Adapter' > Wizard should open on Sign-In page with recent OpenShift 3 connection. > Without PR 'Advanced' button is cropped, with PR it is fully visible. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23708: ------------------------------------- Workaround Description: pick "Show In > Web Console in the context menu and inspect the logs there. Workaround: Workaround Exists > 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 > 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 > # 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! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23708: ------------------------------------- Description: steps to reproduce: # ASSERT: make sure that you have a build that failed # 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! was: steps to reproduce: # ASSERT: make sure that you have a build that failed # EXEC: in Properties view: select the build and choose "Build Log" 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! > 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 > 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 > # 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! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23154) tests: should have sonar checking our pull requests

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23154?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-23154. ------------------------------- Sonar seems to be running fine, closing. > tests: should have sonar checking our pull requests > --------------------------------------------------- > > Key: JBIDE-23154 > URL: https://issues.jboss.org/browse/JBIDE-23154 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: pull_request, quality, test > Fix For: 4.4.3.AM1 > > > Sonar being run in the background tends to get forgotten. I'd therefore love to have sonar testing our pull requests. > Docs for the sonar github plugin are here: http://docs.sonarqube.org/display/PLUG/GitHub+Plugin -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23708: ------------------------------------- Attachment: cannot-get-logs-for-erroring-build.png > 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 > 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 > # EXEC: in Properties view: select the build and choose "Build Log" > 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! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23708: ------------------------------------- Attachment: webconsole-logs-for-erroring-build.png > 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 > 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 > # EXEC: in Properties view: select the build and choose "Build Log" > 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! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23708: ---------------------------------------- Summary: 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 steps to reproduce: # ASSERT: make sure that you have a build that failed # EXEC: in Properties view: select the build and choose "Build Log" 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! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23708: ------------------------------------- Labels: logs properties (was: ) > 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 > > steps to reproduce: > # ASSERT: make sure that you have a build that failed > # EXEC: in Properties view: select the build and choose "Build Log" > 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! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2017