He means the Apache Tomcat manager app. It provides the means to programmatically deploy to Tomcat. JBoss has similar functionality exposed through its management services, though you may have to enable/secure it. This assumes your server lives longer than a deployment, which is not how everyone does it. On Aug 20, 2015 8:05 PM, "Martin" <[email protected]> wrote:
> Hi, Jeff: > > What do you mean by the "manager application" in the description of > "manager application to be installed and configured"? Is it Nexus? Thanks. > > On Thursday, August 20, 2015 at 7:43:34 PM UTC-4, Jeff Vincent wrote: >> >> I don't know anything about JBoss, but Apache (Tomcat) doesn't 'grab' >> anything. You have to push the build to the server either using the tomcat >> manager API or use some other mechanism (SCP, wget, etc.) to otherwise grab >> the WAR file and get it onto the server. >> >> Jenkins has the 'deploy war/ear to a container' plugin to facilitate >> this, but it requires (in the case of tomcat) the manager application to be >> installed and configured. If your production environment is like ours, >> they will not install the manager application so it is either >> copied/configured manually or you can script it via a provisioning tool >> (SaltStack, Chef, Ansible, Puppet, etc.) and there are numerous ways to do >> it through any of those tools. >> >> >> >> On Thu, Aug 20, 2015 at 5:12 PM, Martin <[email protected]> wrote: >> >>> If I use Nexus OSS as a repository manager, the normal for code goes to >>> production system is something like below: >>> >>> 1) Jenkins grabs code from Perforce or GIT server >>> 2) Jenkins retrieves dependencies from Nexus >>> 3) Jenkins test and build the project >>> 4) The build is deployed to Nexus from Jenkins >>> 5) Web application server, i.e. JBoss Application Server or Apache >>> Server grabs code from Nexus, for production service. >>> >>> In this flow, the build in Jenkins doesn't directly go or deploy to Web >>> server, but first parked at Nexus, and goes to Web server. >>> >>> Is this understanding right? I would appreciation an explanation for >>> this cycle. >>> >>> -- >>> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/5ff2816c-3d23-42f4-bfde-103e7f8626fb%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/5ff2816c-3d23-42f4-bfde-103e7f8626fb%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Jeff Vincent >> See my LinkedIn profile at: >> http://www.linkedin.com/in/rjeffreyvincent >> > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/e1a17020-6646-49db-b8d8-b95d30c11886%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/e1a17020-6646-49db-b8d8-b95d30c11886%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0EKvu%3DdnAw8PLHvUtcHQCPxd3bYVLYBtMKXS9Sk4xVd8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
