[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23626:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.3.Final)
> Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23626
> URL: https://issues.jboss.org/browse/JBIDE-23626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Labels: oc_binary, preferences
> Fix For: 4.4.4.AM2
>
>
> oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use.
> Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23660) CDK Server adapter should have an option to configure stop command
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23660?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23660:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.3.Final)
> CDK Server adapter should have an option to configure stop command
> ------------------------------------------------------------------
>
> Key: JBIDE-23660
> URL: https://issues.jboss.org/browse/JBIDE-23660
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: cdk
> Affects Versions: 4.4.2.Final
> Reporter: Ricardo Martinelli Oliveira
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM2
>
>
> CDK Server adapter lets configure the vagrant startup options. There should have an option to do the same in the stop.
> Why?
> It seems that CDK Server adapter uses _vagrant destroy_ to stop CDK, but using that option has its drawbacks, like for example:
> * If I'm stopping it to save resources, then I'm loosing all my job in it.
> * All images already pulled will be lost, so I cannot work offline
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23708:
-------------------------------
Affects Version/s: 4.4.3.AM1
(was: 4.4.4.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.4.AM2
>
> 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, 1 month
[JBoss JIRA] (JBIDE-23708) Pod Log: unable to get build log if build failed with error
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23708?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23708:
-------------------------------
Fix Version/s: 4.4.4.AM2
(was: 4.4.3.Final)
> 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.4.AM2
>
> 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, 1 month