• Email
  • Favorite
  • Download
  • Embed
  • Private Content

Automated Java Deployments With Rpm

by Martin Jackson on Oct 28, 2011

  • 5,883 views

Using the RPM Maven Plugin to package Java Artefacts for fun and profit.

Using the RPM Maven Plugin to package Java Artefacts for fun and profit.

Accessibility

Tags

devops continuous integration java maven jenkins rpm deployment build deploy java maven rpm automation packaging ci

More...

Upload Details

Uploaded via SlideShare as Adobe PDF

Usage Rights

© All Rights Reserved

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel

6 Embeds 395

http://agile.dzone.com 176
http://blog.nikedev.com 133
http://uncommonsense-uk.com 60
http://paper.li 11
http://a0.twimg.com 8
http://java.dzone.com 7

Statistics

Favorites
20
Downloads
83
Comments
4
Embed Views
395
Views on SlideShare
5,488
Total Views
5,883

14 of 4 previous next Post a comment

  • dserodio dserodio Are the config files only in Puppet, or are they also in the RPM? In case they're not in the RPM, how do you exclude them? 1 month ago Reply
    Are you sure you want to Yes No
  • actionjackx Martin Jackson , Freelance Linux Build, Deployment & Release Consultant, Devops advocate, Infrastructure as Code Hacker and keen Judoka at Uncommon Sense Consulting We actually do put the settings into our puppet configuration maybe it wasn't clear in the presentation (I'm planning on moving to Hiera as well).
    The initial problem was because the environment was not externalized and they were shipped with just the development parameters, deployments were problematic i.e. we could not guarantee that the application would work consistently without puppet being running twice.
    7 months ago Reply
    Are you sure you want to Yes No
  • bryanwb Bryan Berry It seems like it would be easier to put the settings for your application in puppet’s hiera or in chef-server’s repository. Then you could use the maven exec plugin to execute knife (or hiera’s equivalent) to get those settings and enumerate the necessary java properties during the build process

    You do describe other advantages or rpms, such as versioning and rollback, that my fix does not offer.
    7 months ago Reply
    Are you sure you want to Yes No
  • schlomo Schlomo Schapiro , Systems Architect / Open Source Evangelist at ImmobilienScout24 We do something similar and will be talking about it at the Velocity Europe (http://velocityconf.com/velocityeu/public/schedule/detail/21669). Hope to see you there and also at http://veubof2011.eventbrite.co.uk/.

    The main difference is that we use Maven to build the RPM and then we use Nexus to store the artifacts that Maven creates, both WAR and RPM.

    We wrote a Nexus YUM plugin that allows direct access to the RPMs hosted on the Nexus as a YUM repo thereby eliminating additional copying steps in our delivery chain.
    7 months ago Reply
    Are you sure you want to Yes No
Post Comment
Edit your comment Cancel

Automated Java Deployments With Rpm — Presentation Transcript