CODEWITHSUNDEEP
javajenkinsdeployment
TheCoder
TheCoder

Reputation: 8933

Jenkins Build and Deploy

I am learning Jenkins. Can someone tell me if my understanding is correct?

To build the app:

To deploy to an environment:

Am I right in saying that a deploy doesn't need to build the latest artefact, that it uses that last one pushed to Nexus, or is a fresh one built every deploy?

Upvotes: 1

Views: 1988

Answers (1)

Lew Bloch
Lew Bloch

Reputation: 3433

It's all according to how you set up your build on Jenkins and/or git.

Jenkins can be configured to monitor your repository (repo, for short) and to kick off a build when it detects a change.

Jenkins can be configured to run a build. You provide the Maven command-line arguments; Jenkins just orchestrates the commands you give it.

Some of the steps you provide Jenkins will be shell code. This is how you can run custom shell scripts, say to access Nexus. Things don't happen by themselves; if you tell Jenkins to deploy an artifact, say by using Maven, then Jenkins will invoke the deployment command as you told it to.

It is highly irregular for an app deployment to arrogate responsibility to start, restart, or shut down your server (Tomcat). That could be done via Jenkins, sure, but it's at a higher "pay grade" than an app deployment should have. Keep it simple; if your Jenkins build is managing an app for testing and deployment, keep its focus on the app and not on the server.

Jenkins is magical, but it's not a mind reader. It will do none of the things you said unless you tell it to. That said, the process you outlined is a reasonable one, whatever tool you use to enact it. Jenkins certainly can do those things, if you set it up accordingly.

Upvotes: 1

Related Questions