[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21857:
---------------------------------------------
is this working now ? I would *love* to see a blog or demo on how to use/do it!
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip
>
>
> 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
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-23470:
-------------------------------------
Workaround Description:
Before any action with server adapter (Stop, Start, Restart in Debug)
1) refresh the corresponding project
2) expand everything by clicking arrows till the running pod
Workaround: Workaround Exists
> Server Adapter: stuck restarting in debug mode
> ----------------------------------------------
>
> Key: JBIDE-23470
> URL: https://issues.jboss.org/browse/JBIDE-23470
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.2.Final
>
> Attachments: failed-to-detect-pod.png, server-adapter-stuck-starting.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with TP and PDE Source Lookup)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23481:
-------------------------------------
Honestly this all sounds like inside implementation details to me :( It would take me a while to understand what half of this stuff even means.
> build target platform sources site (for use with TP and PDE Source Lookup)
> --------------------------------------------------------------------------
>
> Key: JBIDE-23481
> URL: https://issues.jboss.org/browse/JBIDE-23481
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
>
> So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to:
> [1] https://github.com/fbricon/pde.source.lookup/
> [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
> * build a targetplatform with all the sources
> * split that repo into two pieces: all the .source files, and everything else
> * regen the metadata (featureandbundlepublisher) in each new repo so that all the features/plugins are uncategorized
> OR...
> * build a targetplatform without the sources
> * transform the .target file so that each IU ends with .source
> * build the target platform repo from the new .target file
> * verify that sources repo includes the sources of nested features, and those features' plugins' sources too
> ----
> Then once we have the targetplatform.source repo, publish that and verify it works with the PDE Source Lookup plugin:
> 1. install the PDE source lookup plugin
> 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site
> 3. for something you want sources, use the plugin and see if it can resolve soources
> ----
> Then, if that works, we can consider adding the new tp.source site into the JBT/devstudio composite sites, along with jbt + tp + central + central tp (or ds + ds tp + central + central tp) as a 5th child site.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21857:
--------------------------------
Fix Version/s: 4.4.2.Final
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip
>
>
> 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
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23486) Build: DeployImageJobtest#testStubImageStreamWhereOneDoesNotExistAndImageIsPublic is failing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23486?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23486 at 11/11/16 10:37 AM:
---------------------------------------------------------------------
[~jeffmaury] Can you please fix this test since you're the author of the patch. I am very unsure on how to fix this. My educated guess is that the assertion is wrong, but I'm not sure at all (spent quite some time without getting to a conclusive result). But then it also looks to me as "latest" being returned by is#getDockerImageRepository() is fishy.
was (Author: adietish):
[~jeffmaury] Can you please fix this test since you're the author of the patch. I am very unsure on how to fix this. My guess is that the assertion is wrong, but I'm not sure at all (spent quite some time without getting to a conclusive result).
> Build: DeployImageJobtest#testStubImageStreamWhereOneDoesNotExistAndImageIsPublic is failing
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-23486
> URL: https://issues.jboss.org/browse/JBIDE-23486
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.2.Final
>
>
> Our tests are failing
> {code}
> testStubImageStreamWhereOneDoesNotExistAndImageIsPublic(org.jboss.tools.openshift.test.ui.job.DeployImageJobTest) Time elapsed: 0.016 sec <<< FAILURE!
> java.lang.AssertionError: expected:<repo/mynamespace/myimagename:latest> but was:<:latest>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.jboss.tools.openshift.test.ui.job.DeployImageJobTest.testStubImageStreamWhereOneDoesNotExistAndImageIsPublic(DeployImageJobTest.java:219)
> {code}
> the failing assertion is the following:
> {code}
> assertEquals(new DockerImageURI("repo/mynamespace/myimagename:latest"), is.getDockerImageRepository());
> {code}
> Starting with [#1677|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/1677/] our jenkins is thus failing.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23486) Build: DeployImageJobtest#testStubImageStreamWhereOneDoesNotExistAndImageIsPublic is failing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23486?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-23486:
----------------------------------------
Assignee: Jeff MAURY (was: Andre Dietisheim)
> Build: DeployImageJobtest#testStubImageStreamWhereOneDoesNotExistAndImageIsPublic is failing
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-23486
> URL: https://issues.jboss.org/browse/JBIDE-23486
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Andre Dietisheim
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.4.2.Final
>
>
> Our tests are failing
> {code}
> testStubImageStreamWhereOneDoesNotExistAndImageIsPublic(org.jboss.tools.openshift.test.ui.job.DeployImageJobTest) Time elapsed: 0.016 sec <<< FAILURE!
> java.lang.AssertionError: expected:<repo/mynamespace/myimagename:latest> but was:<:latest>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:834)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.jboss.tools.openshift.test.ui.job.DeployImageJobTest.testStubImageStreamWhereOneDoesNotExistAndImageIsPublic(DeployImageJobTest.java:219)
> {code}
> the failing assertion is the following:
> {code}
> assertEquals(new DockerImageURI("repo/mynamespace/myimagename:latest"), is.getDockerImageRepository());
> {code}
> Starting with [#1677|http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_master/1677/] our jenkins is thus failing.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months