-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions about Trooper #32
Comments
You are right, Trooper does allow you to deploy jobs (job binaries, config and dependency binaries) on the fly and not require a restart of the console/app. It also has the ability to propagate these deployments across a cluster, if you use the batch-HA mode. All of these are however done on a per-job basis. We prefer it this way as we can maintain job specific config files, classpaths and eventually job-specific Spring application contexts. The good news however is that we use Spring MVC and Http GET/POST to retrieve/update job configurations and dependencies. It is therefore quite possible to add another method in the controller with appropriate @RequestMapping to receive and process a "fat" jar that follows the structure that you have described. The controller can unpack the jar and deploy jobs individually as is done currently. Is this something you might consider implementing? The code is reasonably contained and is in org.trpr.platform.batch.impl.spring.web.JobConfigController |
Closing this issue as it is not a feature we want to implement now. |
Hi!
I'm checking out Trooper, it looks like a terrific product that you've built on top of Spring Batch Admin!
We really like how you've added in the capability to upload entire jobs. We would like to have a standalone console that enables us to simply add jobs without having to redeploy the entire console, and it appears that Trooper provides this.
/META-INF/spring/batch/jobs
) with XML job configurations and all dependencies of the job.Thanks!
The text was updated successfully, but these errors were encountered: