The Brave New World of Continuous Release

Baruch, JFrog

Baruch Developer Advocate @JFrog

> Job definition (part of): Hang out with the DevOps guys

@jbaruch

About me

JAX Conference San Francisco 2012

The cloud silver bullet The right tool for the job Binaries all the way The magic of release

Agenda

Everything *aasThe New Silver Bullet

What’s So Good About *aaS?

*aaS features Continuous Delivery

User advantages> Latest version/features> No upgrades/maintenance

Developer advantages> Agile> Rapid feedback> Users are the best beta-testers> No long-term support

Everybody wins?

Continuous Delivery FTW

Used to quarterly release cycles “Secure” pace Minimizing the entropy caused by

developers with ADD

Almost, except the IT

Herding Cats

Developers> Increasing entropy

+IT (operations)

> Maintaining stability

=DevOps

> Stable change

8JAX Conference San Francisco 2012

Continuous Delivery Challenge

Very frequent releases More than one version in production Complicated access levels Root cause analysis

> Tracing from binaries to source

Version tracking Not everyone is ready for CD

Continuous Delivery Challenge

Very frequent releases More than one version in production Complicated access levels Root cause analysis

> Tracing from binaries to source

Version tracking Not everyone is ready for CD

It’s… Agile!

Agile principles applied for DevOps We have good tooling for Agile

development> Version control> Unit testing and code coverage> CI servers> Hot swap tools

What’s up with tooling for agile DevOps?

Agile Tooling for DevOps Checklist

Versioning Access control Traceability Promotions Tags and

annotations Search

How Do I Know?

Artifactory is released with Artifactory

JFrog SaaS offering> Artifactory Online> Gradle, Grails, SpringSource,

Typesafe, Jenkins, etc.

We build, release and eat our own dog food> Continuously

Here Comes Binary RepositoryThe Right Tool for the Job

Here Comes Binary Repository

E.g. Artifactory Proxy Smart storage

> Much more than a passive space

Critical for CI/CD and ALM

Tooling Chain

In the Beginning it was…

Binary Repo in DevOps Ecosystem

From some point product in your lifecycle, all you care about is binaries

Lots of things to do after the software is built

Binaries All the Way

The Release Pipeline

Source: Agile ALM, Michael Hüttermann, Manning Publications Co.

Passing the software to QA

Different access rights Different physical location Ability to annotate

Staging and Preproduction

Replication of Production environment> Lock versions of dependencies and artifacts

Allow access to set of users

Going to Production

Convert staging binaries to production Allow public access Change settings Tag

TraceabilityWhy and How?

Sometimes you need to go back in time

The Time Machine

Quest for Traceability

What should be restored?> Sources > Dependencies> Environment details> Tags

Where’s the information?> Version control system> Build Tool> Build server

Checkout branch/tag/revision Build Done!

Time consuming Unstable

Rebuilding from Sources

Dependency Descriptors aren’t stable

Dependencies Lie

POMs deployed with variables> Ivy is OK

Resolution strategies change over time

Evil Dependencies Resolution

Record information on spot> When binaries are created

Build Server

Single Source of Truth

Truth should be saved… … with the binaries… … in binaries storage!

Single Target of Truth

Bill of Materials JSON REST accessible API accessible APLv2 on GitHub

Open Standard Of Truth

Build Server Plugin

Build information> Resolved and realized during the build> Attached to the artifacts> Uploaded with the

artifacts

Artifacts + Build Info = 4eva!!11

Demo Time!Tracing Artifacts

What my friends think I doDevOps

What Others Think I Do

What I Think I Do

What I Really Do

What I should Do

Target: Automation

It’s impossible to release frequently with manual procedures> While maintaining quality

Use your binaries storage to release

The magic of ReleasePut your repository to work

Release Candidates

Your next build is a release-candidate Once successfully built and tested, click

the button> Automatic versions switch> From integration to release

> Right place to put your binaries> Move from Staging to Public

> Automatic VCS tagging

Releasing with Release Candidates

Process:1. Produce and build snapshots until satisfied2. Once satisfied, build a release candidate3. Stage RC, check and verify4. Once verified, release

Releasing With Artifactory Plugin

Changes versions in build script Allows choosing a target deploy

repository Creates a VCS tag/branch

Demo time!Release With Release Candidates

OOTB Release Management

Pros> Out of the box> Supports the “by

the book” release cycle

> Supports majority of the tools

Cons> Limited

extensibility> May not fit your

requirements

JAX Conference San Francisco 2012 47

Process:1. Produce and build snapshots until satisfied2. Once satisfied, build a release candidate3. Stage RC, check and verify4. Once checked, release

Process:1. Produce and build snapshots until satisfied2. Once satisfied, build release candidate3. Stage RC, check and verify4. Once checked, release

Redundant build

Releasing with Release Candidates?

Lots of things can go wrong during one more build

If we won’t build it, we won’t screw it Revised Process:

1. Produce and build snapshots until satisfied2. When satisfied, check and verify3. Once checked, release

Automation Flexibility

YMMV (great deal) Write your own release logic

Pre and post build deploy hooks

We Know: We Don’t Know Better

Controlling Versioning Scheme

Classic versioning scheme:> Release version > 2.0.3

> Integration version> 2.0.4-SNAPSHOT

Flexible Release

Code your release strategy> Versioning scheme> VCS (tagging, branching, commit comments)> Promotion hook (copy/move, comments,

status)

Available by REST

REST == Scriptability == Automation

It’s impossible to release frequently with manual procedures> While maintaining quality

Use your scriptable binaries storage to release

Example: Promotion of Snapshots

Choose existing build to become a release

Using REST API without build server Invoke promotion plugin

> Convert to next version> Tag, branch, etc.> Promote (copy/move)

Code time!Plugin What?

Artifactory is open for user plugins Groovy groovy DSL Your code runs inside the server Uses Public API (PAPI)

> Search for artifacts> Search for builds> Copy/move artifacts> Manipulate files> E.g. change versions in descriptors

Pluggable Architecture with DSLs

https://github.com/JFrogDev/artifactory-user-plugins

Community Effort

As a response for various events> Download/Create/Delete> Login> Release

Scheduled On demand

Plugin Invocation Options

Plugin Code

Manipulating Version Control Systems

Plugin Code

Manipulating BuildInfo object

Plugin Code

Creating and replacing artifacts

http://repo-demo:8080/artifactory/api/plugins/build/promote/snapshotToRelease/gradle-

multi-example/1?params=snapExp=d14|targetRepository=gradle-release-local

Calling REST API With CURL

http://repo-demo:8080/artifactory/api/plugins/build/promote/snapshotToRelease/gradle-multi-example/1?params=snapExp=d14|targetRepository=gradle-release-local

Artifactory server

Plugins API

Artifactory server

Plugins API

Plugin name

Artifactory server

Plugins API

Plugin name

Build name and number

Artifactory server

Plugins API

Plugin name

versioning scheme

Artifactory server

Plugins API

Plugin name

versioning scheme

Target repository for release

Recap: Promotion of Snapshots

Choose existing build to become a release

Using the REST API without building Invoking the promotion plugin

> Convert to next version> Tag, branch, etc.> Promote (copy/move)

Demo time!Release by Snapshot Promotion

4 Commandments of DevOps

Automate everything

Version everything

Trace everything Report/Log/Feed

back everything Designed by Jessica Allen on Dribbble.com

4 Commandments of DevOps

Automate everything

Version everything

Trace everything Report/Log/Feed

back everything Designed by Jessica Allen on Dribbble.com

The Brave New World of Continuous Release - Baruch Sadogursky

Transcript of The Brave New World of Continuous Release - Baruch Sadogursky

The Brave New World of Continuous Release - Baruch Sadogursky

Technology

Transcript of The Brave New World of Continuous Release - Baruch Sadogursky

Baruch Spinoza - Biography

AIESEC Baruch Annual Report

BARUCH SENIOR MINISTRIESbaruchsls.org/wp-content/uploads/2015/09/2010-BARUCH-ANNUAL-… · Spiritual Care 4 New at Baruch 5 2010 Revenues and Expenditures 6 Baruch Team 7 Community

Baruch 09. business writing

2001 BRAVE / BRAVE SE - Winnebago

Book 2 of Baruch

Baruch College Women's Basketball

4th Baruch

Spinoza Baruch - Tratado Politico

Spinoza Baruch-The Ethics

ADMISSIONS REPORT - Baruch CollegeIn 2015, Baruch College was once again ranked among America’s “Best Value Schools” by Forbes magazine. Baruch College’s annual tuition for

Baruch College Viewbook

Baruch Grassroots Meeting 6

AND THE GUIDELINES FOR PROCUREMENT CONTRACTS That … · Baruch Library Master Plan Baruch Student Computer Lab Baruch Student Computer Lab Baruch - Stud ~nt Computer Lab BMCC ADA

Aventis Baruch

Brave Buyers Guide - Brave Browser

Baruch Marketing Brochure

Presentation Baruch Version

Baruch Spinoza

ADMISSIONS REPORT - Baruch College...In 2015, Baruch College was once again ranked among America’s “Best Value Schools” by Forbes magazine. Baruch College’s annual tuition