[JBoss JIRA] (JBIDE-23033) Spring Planning Script
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-23033:
-----------------------------------
Summary: Spring Planning Script
Key: JBIDE-23033
URL: https://issues.jboss.org/browse/JBIDE-23033
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: upstream
Affects Versions: 4.4.1.AM3
Reporter: Rob Stryker
Assignee: Rob Stryker
A script for the sprint planning meeting should be made. This script should help facilitate the following goals:
1) Devs should give a general idea of the main issues they are targeting for the sprint
2) Devs should indicate if they are fully booked with top-priority issues, or can bump some for others who need help
3) Devs should indicate if they have critical or major issues that need help that are not targeted to this sprint
4) QE, having more experience using the tools every day for months in both clean and dirty workspaces, should act partly as a project owner
4a) QE should list what they perceive as the most troublesome or annoying issues for the component they test (or other components)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ]
Jeff Cantrill reassigned JBIDE-23030:
-------------------------------------
Assignee: Jeff Cantrill
> Scaling a service changes the wrong deployment
> ----------------------------------------------
>
> Key: JBIDE-23030
> URL: https://issues.jboss.org/browse/JBIDE-23030
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Critical
>
> In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift.
> The workaround is to open the properties view and issue a scale command on a deployment directly.
> However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-23030:
---------------------------------------
[~fbricon] Challange accepted
> Scaling a service changes the wrong deployment
> ----------------------------------------------
>
> Key: JBIDE-23030
> URL: https://issues.jboss.org/browse/JBIDE-23030
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Critical
>
> In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift.
> The workaround is to open the properties view and issue a scale command on a deployment directly.
> However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22375) Improve HCR OpenShift
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22375?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22375:
--------------------------------
Sprint: devex #114 May 2016 (was: devex #114 May 2016, devex #119 August 2016)
> Improve HCR OpenShift
> ---------------------
>
> Key: JBIDE-22375
> URL: https://issues.jboss.org/browse/JBIDE-22375
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.4.x
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22375) Improve HCR OpenShift
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22375?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22375:
--------------------------------
Sprint: devex #114 May 2016, devex #120 September 2016 (was: devex #114 May 2016)
> Improve HCR OpenShift
> ---------------------
>
> Key: JBIDE-22375
> URL: https://issues.jboss.org/browse/JBIDE-22375
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.4.x
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23031) OpenShift can't push Docker Images with latest Docker Neon.1 bits
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-23031:
-----------------------------------
Summary: OpenShift can't push Docker Images with latest Docker Neon.1 bits
Key: JBIDE-23031
URL: https://issues.jboss.org/browse/JBIDE-23031
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: docker, openshift
Environment: DevStudio 10.1.0.AM3
Docker Tooling 2.1.0.201608221023
Reporter: Fred Bricon
Priority: Blocker
After installing Docker Tooling 2.1.0.201608221023 on top of Devstudio 10.1.0.AM3, when I try to push a docker image to openshift, I get this error:
{noformat}
java.lang.NoClassDefFoundError: org/eclipse/linuxtools/internal/docker/ui/views/ImagePushProgressHandler
at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:66)
at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.ClassNotFoundException: org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler cannot be found by org.jboss.tools.openshift.ui_3.3.0.v20160812-0126
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 3 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months