[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 edited comment on JBIDE-23622 at 1/4/17 11:32 AM:
-------------------------------------------------------------------
[~mlabuda] To me your initial bug request was nothing unexpected. One 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?
was (Author: adietish):
[~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
> Assignee: Jeff MAURY
> 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, 3 months
[JBoss JIRA] (JBIDE-23019) Integration tests: have them running automatically, continuously
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23019?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23019:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Integration tests: have them running automatically, continuously
> ----------------------------------------------------------------
>
> Key: JBIDE-23019
> URL: https://issues.jboss.org/browse/JBIDE-23019
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.3.AM2
>
>
> The integration tests suite is very lenghty to run and should thus be run in a continuous manner on our CI.
> There are several pain-points currently:
> - there's no dedicated OS instance to run them against
> - tests are not stable
> - etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-21593) Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21593?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21593:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Application wizard: Opening wizard and creating required project (clean connection) makes wizard unusable
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21593
> URL: https://issues.jboss.org/browse/JBIDE-21593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: Fedora 22, GTK 3.
> Reporter: Marián Labuda
> Labels: application_wizard, explorer, openshift_v3
> Fix For: 4.4.3.AM2
>
> Attachments: empty_project.png
>
>
> When I am opening a new OpenShift application wizard on OpenShift 3 connection where are no projects yet, at first project dialog to create a new project is opened. Upon creation of a new project, dialog is closed and I am "redirected" back to application wizard, where newly created project should be preselected. Problem is the new project is shown as empty tree item in OpenShift explorer (this happens also if new project dialog is opened directly from the context menu of a clean connection) what makes new OpenShift application wizard unusable, because there are no projects in combo, no matter what. See following screenshot
> !empty_project.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-19506:
-------------------------------------
Fix Version/s: 4.4.3.AM2
(was: 4.4.3.AM1)
> Connection wizard, Connection: should have unit tests
> ------------------------------------------------------
>
> Key: JBIDE-19506
> URL: https://issues.jboss.org/browse/JBIDE-19506
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, tests
> Fix For: 4.4.3.AM2
>
> Original Estimate: 2 days
> Time Spent: 3 days
> Remaining Estimate: 3 days
>
> In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods when no service is available
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23490:
-------------------------------------
Labels: new_and_noteworthy openshift_v3 server_adapter server_adapter_wizard (was: new_and_noteworthy)
> Server adapter: provide ability to link pods when no service is available
> -------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.AM1
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods when no service is available
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23490:
-------------------------------------
Summary: Server adapter: provide ability to link pods when no service is available (was: Provide ability to link pods when no service is available)
> Server adapter: provide ability to link pods when no service is available
> -------------------------------------------------------------------------
>
> Key: JBIDE-23490
> URL: https://issues.jboss.org/browse/JBIDE-23490
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard
> Fix For: 4.4.3.AM1
>
>
> When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application.
> The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months