[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25303:
------------------------------------
I also don't get it. I agree that dealing with BOOT-INF/classes is a matter of the server adapter.
Now I think that the temporary folder that is prepared by WTP should reflect the JAR nature so we should find updates classes and resources there, no ?
> Server adapter: support hot-deployment on OpenShift for SpringBoot app
> ----------------------------------------------------------------------
>
> Key: JBIDE-25303
> URL: https://issues.jboss.org/browse/JBIDE-25303
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.2.AM2
>
> Attachments: fuse-on-openshift.zip, project-deployment-assembly.png, spring-boot-demo.zip
>
>
> currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file.
> The requirements are:
> - rsync unpacked jar
> - rsync without the jar name as folder
> - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated)
> use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools":
> - there is a SpringBoot app deployed on OpenShift
> - the developer want to develop evolution of the SpringBoot app
> -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance
> -- Remote java debug should be available when the OpenShift server adapter is in debug mode.
> Steps:
> # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot)
> # EXEC: Import project within fuse-on-openshift.zip into your workspace
> # EXEC: open launch configuration and change:
> ** -Dkubernetes.master= so that it first your cdk instance
> ** -Dkubernetes.namespace= to the name of the project that you create in step 1.
> # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk)
> # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running.
> # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service)
> # ASSERT: server adapter is created and is *[started]*
> # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service)
> # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end
> {code}
> simple-route - >>> 455
> simple-route - >>> 695
> simple-route - >>> 935
> {code}
> # EXEC: In Project Explorer: open class MyTransformer and change the transform method
> # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBDS-4629) CDK description inconsistent with other components
by Robin Owen (JIRA)
[ https://issues.jboss.org/browse/JBDS-4629?page=com.atlassian.jira.plugin.... ]
Robin Owen commented on JBDS-4629:
----------------------------------
Closing this issue on JIRA, as it applies to the upstream developer-platform-install repo on GitHub.
Relevant issue on GitHub: [Issue #1093: CDK description inconsistent with other components|https://github.com/redhat-developer-tooling/developer-platform...]
> CDK description inconsistent with other components
> --------------------------------------------------
>
> Key: JBDS-4629
> URL: https://issues.jboss.org/browse/JBDS-4629
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Robin Owen
> Priority: Minor
>
> At present, the description for CDK in the DevSuite installer is title cased. This is inconsistent with every other component of the installer.
> Currently, the description reads as follows:
> "Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications"
> This is also a bit vague, not mentioning the fact that CDK runs a single-node OpenShift cluster in a local VM to assist with containerized application development.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBDS-4629) CDK description inconsistent with other components
by Robin Owen (JIRA)
[ https://issues.jboss.org/browse/JBDS-4629?page=com.atlassian.jira.plugin.... ]
Robin Owen resolved JBDS-4629.
------------------------------
Resolution: Duplicate
> CDK description inconsistent with other components
> --------------------------------------------------
>
> Key: JBDS-4629
> URL: https://issues.jboss.org/browse/JBDS-4629
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Reporter: Robin Owen
> Priority: Minor
>
> At present, the description for CDK in the DevSuite installer is title cased. This is inconsistent with every other component of the installer.
> Currently, the description reads as follows:
> "Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications"
> This is also a bit vague, not mentioning the fact that CDK runs a single-node OpenShift cluster in a local VM to assist with containerized application development.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBDS-4629) CDK description inconsistent with other components
by Robin Owen (JIRA)
Robin Owen created JBDS-4629:
--------------------------------
Summary: CDK description inconsistent with other components
Key: JBDS-4629
URL: https://issues.jboss.org/browse/JBDS-4629
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Enhancement
Components: platform-installer
Reporter: Robin Owen
Priority: Minor
At present, the description for CDK in the DevSuite installer is title cased. This is inconsistent with every other component of the installer.
Currently, the description reads as follows:
"Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications"
This is also a bit vague, not mentioning the fact that CDK runs a single-node OpenShift cluster in a local VM to assist with containerized application development.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25446) Windows/Mac slave gets disconnected during job execution
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25446?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25446:
---------------------------------------
[~psrna] Done!
Please, see: https://redhat.service-now.com/surl.do?n=PNT0115451
> Windows/Mac slave gets disconnected during job execution
> --------------------------------------------------------
>
> Key: JBIDE-25446
> URL: https://issues.jboss.org/browse/JBIDE-25446
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Blocker
> Labels: jenkins
>
> During jenkins job execution slaves is disconnected with exception
> {code}
> 19:09:27 19:09:27.096 DEBUG [WorkbenchTestable][AbstractWait] Waiting until shell matching Matcher matching when all matchers match: [Matcher matching widget which text matches: "Problem Occured"] is available....
> 19:09:32 FATAL: command execution failed
> 19:09:32 java.io.IOException: Backing channel 'Channel to /10.8.247.148' is disconnected.
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:191)
> 19:09:32 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256)
> 19:09:32 at com.sun.proxy.$Proxy68.isAlive(Unknown Source)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043)
> 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035)
> 19:09:32 at hudson.Launcher$ProcStarter.join(Launcher.java:399)
> 19:09:32 at hudson.tasks.Maven.perform(Maven.java:367)
> 19:09:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
> 19:09:32 at hudson.model.Build$BuildExecution.build(Build.java:205)
> 19:09:32 at hudson.model.Build$BuildExecution.doRun(Build.java:162)
> 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
> 19:09:32 at hudson.model.Run.execute(Run.java:1728)
> 19:09:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
> 19:09:32 at hudson.model.ResourceController.execute(ResourceController.java:98)
> 19:09:32 at hudson.model.Executor.run(Executor.java:404)
> 19:09:32 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5af9151e[name=Channel to /10.8.247.148]
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:635)
> 19:09:32 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
> 19:09:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 19:09:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 19:09:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 19:09:32 at java.lang.Thread.run(Thread.java:748)
> 19:09:32 Caused by: java.io.IOException: Connection reset by peer
> 19:09:32 at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
> 19:09:32 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
> 19:09:32 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
> 19:09:32 at sun.nio.ch.IOUtil.read(IOUtil.java:197)
> 19:09:32 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:142)
> 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:359)
> 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564)
> 19:09:32 ... 6 more
> 19:09:32 Build step 'Invoke top-level Maven targets' marked build as failure
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months