I'm in a company that builds both .NET & Java applications. I want to be able to use a common process to deploy previous built applications to target servers. To further complicate issues, I have to be able to deploy code to both in-house, cloud, and client side servers. I use Jenkins as my CI tool and have used it in the past for deployments. Most of our applications have deployment pipelines that are for in-house and clients-side servers.
I'm curious how to best use Jenkins in a consistent manner for managing deployments in our environment. The CI process builds my deployment packages and will have scripts to performing the deployment on the target server, I just need to be able to set up Jenkins to runs the builds on each server. I was reading up on using docker to provision slaves-on-demand. I would like to be able to start up a slave on the client side deploy the code and then shut it down. I think that since it goes over http and is a temporary service running, they will accept this. We have many different government agencies for clients and I need to be able to show a consistent and secure way of perform the deployments. Does anybody have a suggestion on how I can use Jenkins for this deployment phase? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.