Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations Build Trust in Your Build-to-Deployment Flow!

Build Trust in Your Build-to-Deployment Flow!



Baruch Sadogursky demonstrates automated building techniques using Maven/Gradle/Custom scripts and Binary Repository along with common pitfalls that are to be avoided.


Baruch Sadogursky recently joined JFrog as the Community Advocate, contributing to the strong collaboration with leading open-source projects such as SpringSource, Grails and Gradle by providing them with the Artifactory Cloud platform, and fueling the Continuous-Integration ecosystem with plugins Jenkins, TeamCity & Bamboo. Blog: & Tweeter:@jbaruch.

About the conference

Software is changing the world; QCon aims to empower software development by facilitating the spread of knowledge and innovation in the enterprise software development community; to achieve this, QCon is organized as a practitioner-driven conference designed for people influencing innovation in their teams: team leads, architects, project managers, engineering directors.

Recorded at:

Jul 12, 2012

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • great job

    by Stanislav Tyurikov,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    I saw this presentation at the JavaOne days in Moscow. Thanks for the T-shirt, Baruch! Good luck!

  • Re: great job

    by Baruch Sadogursky,

    Your message is awaiting moderation. Thank you for participating in the discussion.


  • Don't change binaries!

    by Esko Luontola,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    The approach of changing a snapshot into a release by modifying the version number is risky. It requires modifying the binaries, in which case they are not anymore the same binaries. Modifying a binary has the same risks as in creating a new build from the source. A better approach is to get rid of snapshots and only create release builds, and then select (automatically or manually) that which of those binaries to promote to production as is.

    Here is one example of how it can be done: Continuous Delivery with Maven and Go into Maven Central

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p