Implement single click deployment using Jenkins and DeployIt

Problem statement : Implement single click deployment using Jenkins and DeployIt
Tools used: Jenkins CI Server, DeplyIt Plugin for Jenkins, Github plugin for jenkins, Maven for building artifact.

Detailed use case :
Lets suppose we have our code in github in a public repository and we want that every fix which goes to “deployment” branch should get propagated to a dev environment automatically.

In order to get this set up working we would need to do:
1.) Configure Jenkins with gitHub and deployIt Plugin.
2.) Configure application placeholder and environment (including infrastructure) in which deployment would take place in DeployIt.

See the solution in my blog posted at Xebee :

http://xebee.xebia.in/index.php/2013/10/16/implement-single-click-deployment-using-jenkins-and-deployit/

Tagged with: , , ,
Posted in continuous delivery, continuous integration
7 comments on “Implement single click deployment using Jenkins and DeployIt
  1. True. I agree with Anirudh…
    Infact there is lot inside Jenkins where
    1) One can integrate pre and post deployment scripts inside jenkins jobs. Checkstyle and findbug reports can be presented on jenkins UI itself by configuring in post deployment steps for any jenkin job.
    2) Test coverage report on test cases(JUnits) can also be presented by configuring the cobertura plugin and coverage metric targets to reflect your goals.
    3) JIRA and Github can also be configured in order to capture SCM changes.

    In nutshell one needs to follow the CI delivery model in today’s s/w development and automate the build and release process as much as possible.

    Thanks,
    Abhishek

  2. 1 quick note : We can write post deployment scripts and use instead of Deployit , perhaps Deployit provides more automated way to create the infrastructuire like Chef and deploy application artifacts on this. What do you say Anirudh?

  3. True. I agree with Anirudh…
    Infact there is lot inside Jenkins where
    1) One can integrate pre and post deployment scripts inside jenkins jobs. Checkstyle and findbug reports can be presented on jenkins UI itself by configuring in post deployment steps for any jenkin job.
    2) Test coverage report on test cases(JUnits) can also be presented by configuring the cobertura plugin and coverage metric targets to reflect your goals.
    3) JIRA and Github can also be configured in order to capture SCM changes.

    In nutshell one needs to follow the CI delivery model in today’s s/w development and automate the build and release process as much as possible.

  4. Luisenaguero says:

    What if i want to deploy to IIS from Jenkins ??? The Deploy Plugin onlye allows Tomcat, JBoss and Glassfish

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 152 other followers

Blog Stats
  • 10,323 hits
Follow

Get every new post delivered to your Inbox.

Join 152 other followers

%d bloggers like this: