[jbosstools-issues] [JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-25303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540091#comment-13540091 ] 

Andre Dietisheim edited comment on JBIDE-25303 at 3/1/18 6:27 AM:
------------------------------------------------------------------

[~jkopriva] to verify if JAVA_DEBUG is set:
In explorer: select the service and pick "Manage Environment Variables...". You then should get vars listed with their values.
When you start the server adapter, the var should get set automatically (you see this in the explorer/properties: when you start the server adapter a new pod is spun up, the old one is terminated). And for me this always happened. So I'd be astonished if it wasnt.

If it is set, then the next question arises: why is the docker image not unpacking the springboot jar in response to the existence of the env variable? The most obvious response would be that you're not using the fabric8/s2i-java base image but the fis image, which hasnt this implemented yet.


was (Author: adietish):
[~jkopriva] to verify if JAVA_DEBUG is set:
In explorer: select the service and pick "Manage Environment Variables...". You then should get vars listed with their values.
When you start the server adapter, the var should get set automatically (you see this in the explorer/properties: when you start the server adapter a new pod is spun up, the old one is terminated). And for me this always happened. So I'd be astonished if it wasnt.

If it is set, then the next question arises: why is the docker image not unpacking the springboot jar in response to the existence of the env variable. The most easy response would be that you're not using the fabric8/s2i-java base image but the fis image, which hasnt this implemented yet.

> 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.3.AM3
>
>         Attachments: Image+Pasted+at+2018-1-16+10-58.png, 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.
>    ** -Dfabric8.generator.from=fabric8/s2i-java
> # 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)