Cloud bees and forester open source is not enough

Open Source: Essential For
Modern Application Delivery
Jeffrey Hammond, Forrester
Vice President & Principal Analyst
Brian Dawson, CloudBees
DevOps Evangelist

© 2017 CloudBees, Inc. All Rights Reserved. 2
Speakers
Jeffrey Hammond, Forrester
Vice President and Principal Analyst
Jeffrey is a software development veteran, with more than
twenty-five years of experience in software development and
delivery. He is a leading expert on mobile development, modern
application architecture, Agile and Dev-ops practices, and open
source policies.
Jeffrey holds a B.S. in economics from the Wharton School.
•
Brian Dawson, CloudBees Inc,
DevOps Evangelist and OSS Marketing Manager
At CloudBees Brian focuses on implementation of agile,
continuous integration (CI), continuous delivery (CD) and
DevOps practices as well as open source products.
Prior to CloudBees, Brian spent over 24 years as a software
professional. Most recently he led an Agile Transformation
Consulting practice helping organizations small and large
implement CI, CD and DevOps.

© 2016 Forrester Research, Inc. Reproduction Prohibited 4
June 29, 2007March 19, 2006
Celebrating a decade of modern
applications

US Tech Market Outlook For 2016 And 2017: Cloud And Business Caution Will Slow Growth
Cloud adoption reaches a tipping point

Software innovation used to be expensive…
“When I built my first company in 1999 it cost $2.5 million in infrastructure
just to get started and another $2.5 million in team costs to code,
launch, manage, market and sell our software. So it’s not surprising that
typical “A rounds” of venture capital were $5 to $10 million.”
Mark Suster, GRP Partners
…but what if innovation with software
now cost 90% less than it used to?

The way we develop has changed…
7 Traits of Modern Applications
1. Omni-channel clients
2. Deployed on elastic
infrastructure
3. Aggregate discrete services
4. Use managed APIs
5. Focus on measurable
feedback and analytics
6. Integrate open source
software
7. Employ dev-ops techniques
Source: Flickr http://upload.wikimedia.org/wikipedia/commons/6/65/HP_garage_front.JPG)

Source: Forrester Business Technographics Global Developer Survey, 2016
Base: 1571 developers (total responses)
Which of the following classes of open source software tools/frameworks
have you used for development or deployment in the past 12 months?
12%
13%
14%
15%
15%
16%
16%
17%
18%
19%
22%
29%
33%
37%
38%
Have not used open source software
Portals or mashup servers
NoSQL DBMSes
Business applications (Sugar CRM, Bravo)
Operating system containers
Integration
Business intelligence tools
Content management systems
Application messaging
Application frameworks
Application server
Development IDEs
Web servers
Operating systems
Relational DBMSes
Open source is everywhere these days

And it’s not just for app infrastructure
“How prevalent are open source software development tools in your delivery pipeline?”
5%
37%
42%
16%
Small role — one or two tools in delivery
pipeline
Medium role — less than half the tools in
our delivery pipeline
Significant role — over half the tools in our
delivery pipeline
Major role — almost all or all of our tools in
the delivery pipeline
Source: A commissioned study conducted by Forrester Consulting on behalf of Cloudbees, June 2016
Base: 150 professionals responsible for software development lifecycle tools purchasing/support/administration in the US

Why are modern apps inexorably OSS?
› OSS trades CAPEX for OPEX
› Traditional licensing models can’t cope with elasticity and
scale out architectures
› A rising tide of social development coupled with a
developer shortage
› Speed of acquisition and deployment
› Innovation is shifting from the Cathedral to the Bazaar
› Millennial developers choose OSS first

Traditional acquisition processes are slow
What CMMI-ACQ recommends

Why delivery speed must vary
The Cynefin Framework

Price
Capability(quality+features)
Substitution
zone
“Cadillac” products
“Honda” products
Innovation and OSS: The Honda and the
Cadillac

Dev-ops innovations drive faster app
delivery
1. Infrastructure as art ➔ infrastructure as code
2. Big batches ➔ small batches
3. Manual builds ➔ continuous integration
4. Manual testing ➔ automated API-driven testing
5. Integrated architectures ➔ loosely coupled services
6. Maximize utilization ➔ maximize throughput
7. “Requirements” ➔ “testable hypotheses”

Modern applications have forced a
“Honda” moment in the Dev-Ops world
Release Release ReleaseRelease ReleaseReleaseRelease
Plan/Align/Build/Test/Accept/Ship
The Release Train Model
Deliveries
Deliveries Deliveries
Deliveries Deliveries Deliveries
Deliveries
Environment cut over

Dev tool innovation shifts to OSS…
“Relative to commercial software development tools, open source
software development tools deliver new capabilities at a . . . ”
5%
12%
29%
44%
11%
Much
slower rate
Slower rate Similar rate Faster rate Much faster
rate

…and quality has reached a tipping point
“Relative to commercial software development tools, the new capabilities
of open source software development tools are . . . ”
4%
8%
37%
39%
13%
Of much lower
quality
Of lower
quality
Of about the
same level of
quality
Of higher
quality
Of much
higher quality

A word of warning to the inexperienced
"Our acquisition of OSS is driven primarily by the
desire to avoid software costs wherever possible,
but we always buy product support because it's less
costly than supporting OSS projects ourselves."
(CTO at a leading travel provider)

Who integrates it, and how?
It integrates easily
without customization
18%
Some customization is needed to
integrate it with our other tools
60%
Extensive customization is
required to make it useful
22%
“What level of effort is required to adopt an open source software
development tool as part of your software delivery tool set?”

Tool security is a top concern
“How satisfied are you with the degree to which the
open source software development tool(s) you use
supports the following capabilities?”
Very satisfied
“Please rank each capability in order of importance
for your open source software development
tool(s).”
Most important
3%
5%
10%
20%
63%
Governance
Dashboards and
analytics
Scalability
Manageability
Security
19%
27%
37%
45%
45%
Security
Governance
Manageability
Dashboards and
analytics
Scalability

Mixed source solutions add value – when
built to support modern applications
Adds significant
value to the open
source tool, 54%
Does not significantly add
to the value of the open
source tool, 27%
Reduces the value
of the open source
tool due to added
complexity, 19%
“When there is a commercial offering built on top of an
open source software development tool, the
commercial offering . . . ”
“When you purchase a commercial extension to an
open source tool, what value does the commercial
offering add?”*
47%
47%
59%
75%
More frequent releases or
patches
Greater perceived long-
term viability
A richer feature set
Improved quality

OSS is an inevitable part of software delivery
› Don’t fight the inevitable – embrace it proactively
› Create a comprehensible policy – with stated goals
› Define your support strategy – elaborate all the options
› Look for “Honda” projects that are ready for modern applications
› Supplement open source with mixed source where it increases value
› Become part of the communities for OSS you deem strategic
› Don't expect perfection, and plan for remediation

DevOps Maturity and CloudeBees Jenkins Solutions
Scaling CD and
DevOps on OSS
Innovation

Poll Question 2
How would you characterize your organizations adoption of CI/Continuous
Delivery?
1. We have not adopted CI or CD
2. We practice CI, but not CD
3. We have implemented CD on some teams
4. We have implemented CD on most or all teams

Process,
Practices and
Tools
Desires Development
and Delivery State
Current Development
and Delivery State
Integration and
Implementation

Fundamentally it’s about...
Delivering
Better
Software
Faster!
Concept-to-Customer
High Quality
• Performance
• Feature
• Function
Rapidly
Eliminating Waste
Market Innovation
High Value

The market is
transforming
71%practice continuous delivery
with deployment to production
What level of automation have
you implemented with Jenkins?
Source: 2016 Jenkins Community Survey
50%
21%
Continuous delivery with manual
deployment to production
Continuous delivery with fully automated
deployment to production

The market is
transforming
61%practicing CD deploy once
per week or more
If you are practicing continuous delivery,
how often do you deploy to production?
Source: 2016 Jenkins Community Survey
15%
4%
23%
19%
19%
20%
Multiple per Wk
Once per Day
Several per Wk
Once per Wk
Once per Mo
Less Often

Introduction to the Four
Quadrants of DevOps
Maturity
30

Framing Enterprise CD
31
Agile
Upstream 33%
Agile
Downstream 13%
Enterprise
Agile Upstream 22%
Enterprise
DevOps 10%
TeamWorkgroupEnterprise
Define Plan Code Build Integrate Test Release Deploy Operate

The Destination
Agile
Upstream 33%
Agile
Downstream 13%
Enterprise
Agile Upstream 22%
• Innovate faster
• Respond to market
• Gain competitive advantage
• Increased productivity
• Employee satisfaction and retention

The Chasms
Upstream Downstream
People &
Culture
Process &
Practices
Tools &
Technology
Agile, Scrum, Kanban PMBOK, ITIL, Waterfall
Point Tools,
Grassroots, Rapid Change
Move Fast, Innovate Maintain Quality Stability, Uptime
Enterprise Class, Corp.
Procurement, Stable

•People, Process and Tools
•CD and DevOps (practically) require automation
•Automation requires tooling
•Tools are the most quantifiable
•OSS provide and agile starting point and foundation, but…
DevOps Trinity and Tools

Tools as the Foundation
Upstream Downstream
People &
Culture
Process &
Practices
Tools &
Technology
Agile, Scrum, Kanban PMBOK, ITIL, Waterfall
Point Tools,
Grassroots, Rapid
Change
Move Fast, Innovate Maintain Quality Stability, Uptime
Enterprise Class, Corp.
Procurement, Stable

Poll Question 2
What is your biggest obstacle in implementing CD/DevOps
1. Changing People and Culture
2. Implementing the Practices and Process
3. Integrating Tools
4. Legacy technology
5. Management support, budget etc

Tools & Technologies enable “crossing the chasm”
Normalized
 Language and
practice
agnostic
 Not Dev or Ops
specific
 Distributed
Rich
Integration
Support
 Tools as
microservices
 Modular
Automated
 Repeatability
 Reportability
 Flexibility
Increase
Confidence In
Downstream
Deliverables
 Support supply-
chain
 Traceability
 Immutability
 Measure and
report
Scale To
Enterprise
 Cross-domain
visibility metrics
 Security and
governance
 Supported

Solution SoupTeamWorkgroupExecutive
Rally
Jira
Misc Point Solutions
Chef
Puppet
HP OO
SVN
Git
NolioMiscellaneous ALM Solutions
HP ALI
TestLink
Helpdesk
Selenium
PPM
XL Release
Nexus
Chat
LDAP
APM
Docker

TeamWorkgroupExecutive
MiscPoint
Solutions
Jira,
TeamForge..
Eclipse,
IntelliJ,SVN,
Git
Jenkins,
Make,
Maven..
Jenkins,CI
Solutions
Selenium,
TestLink…
XLRelease,
HPOO…
XLRelease,
HPOO…
Chat,
Logging,
Monitoring
LDAP, SAML
Product Portfolio
Application Performance Mgt
Service Desk
Integrate and Automate

MiscPoint
Solutions
JIRA,
TeamForge..
Eclipse,
IntelliJ,SVN,
Git
Jenkins,
Make,
Maven..
Jenkins,CI
Solutions
Selenium,
TestLink…
XLRelease,
HPOO…
XLRelease,
HPOO…
Chat,
Logging,
Monitoring
Security, Scalability and Manageability
Integrate and Automate
Security and Access Controls
Reporting and Analytics
Supply Chain Managment
Shared Infrastructure

On the only
secure, scalable
& supported
Jenkins based
platform
We help you
continually
deliver better
software to fuel
your business
We are the Jenkins experts
Software
at the speed
of ideas

Code & Commit Build & Config Scan & Test Release Deploy
Over 1.2 Million users 1200+ plugins cover every
stage of delivery
Jenkins is the hub of Continuous Delivery

Challenges with Jenkins in the enterprise
Manageability ScalabilitySupport Security

Security & compliance
Scale & operations
Control & visibility
Enterprise
Continuous
Delivery
Requirements
for continuous
delivery at scale
Knowledge and Expertise

CloudBees Jenkins Enterprise

CloudBees Jenkins Enterprise solves the automation
needs of organizations that need scalability, security,
manageability and resiliency capabilities, built on a cloud-
native architecture.
The Continuous Delivery Platform Architected for the Enterprise

CloudBees Jenkins Enterprise

Solution Overview: Key Components

How CloudBees protects your build infrastructure
50© 2016
Day 1 : Zero-day Jenkins vulnerability discovered
• Public announcement with work-around
• Security alert email sent to customers
Day 5 : Security issue patched & released
• Patch notification email to customers
Ongoing : Continued verification of Jenkins bits & plugins
Fix developed & tested

CloudBees Jenkins Enterprise Features & Benefits
Scalability
• Reduce infrastructure cost with containers
• Resilient jobs that resume in case of server failures
• One-click provisioning for onboarding new teams and project
Manageability
• Scale to teams of any size using Distributed Pipeline Architecture
• Host Jenkins anywhere, on-premise or in the cloud
• Minimize hardware requirements with elastic agents
• Isolate team-sensitive build agents
• Includes enterprise grade security
• Store infrastructure credentials in configuration vaults
Security

CloudBees Jenkins Subscription Benefits
Support Model
• Free training
• Knowledge repository for best practices and Jenkins tips & tricks
• Direct access to the leading Jenkins experts
CloudBees
Network
• 24/7 support options
• Security patches
• Expert (Dev-level) support engineers
• Deployment and upgrade confidence (boring upgrades)
• Curated, verified community plugins
• Continuous innovation with verified monthly releases
CloudBees
Assurance
Program

Distributed Pipeline Architecture
The foundation for enterprise DevOps success

CD Enables Speed
A single CD pipeline provides your
team speed with little instability...

But as CD Scales Business Risk Increases
As other teams adopt CD instability
increases and speed decreases

With CloudBees, Continuous Scaling Just Works
DPA enables scale with isolated, on-
demand containerized CD servers for
each of your team
...in fact you can move faster

CloudBees customers are faster
“18 days to 4 days”
5x
FASTER
“From 6 hours to 40 minutes”
9x
FASTER
“Once a day to four times a day”
4x
FASTER

Task Before After
Speed Increase e.g.
“n times faster”
Metrics (what it means)
Axciom adding users 4 hours (240 minutes) .5 minute 48.00 480% faster
ArtStor server provisioning 1 days +
(8 hours or 480 minutes)
15 minutes 32.00 320% faster
Global Bank build monitoring .5 day 0 Eliminated Saves 20 person hours/mo
Choose digital development time 3-5x faster 5.00 500% faster development
cost 10-15x Reduced delivery costs up to 15%
GROUPE
ADEO
project setup 5x faster 5.00 500% faster setup
downtime 2 days 0 eliminated Zero downtime
upgrading systems 3 days 0 eliminated Reclaimed 3 person days
Netflix build feedback 15+ minutes (900 seconds) 10 seconds 90.00 90x faster feedback to Dev
Semiconductor
manufacture
build times 4 hours .5 hour 8.00 800% faster builds
backup 1 week/year Reclaimed 1 week per year
Neustar development time (use 4 days) 25% reduction (use 3 days) 1.33 25% reduction in dev time
build frequency 1/day 4x/day 4.00 400% faster builds
Orbitz release cycles 18 days 3.5 days 5.14 Release in 4 days instead of 3 weeks
a/b test production push 2 weeks (15 days) 3 days 4.67 Push in 3 days instead of 2 weeks
TeleStax bug fixes 20% faster 0.75 20% faster at bug fixes
Viridity Energy deployment 20 hours < 1 hour 20.00 Reduced from hours to minutes
build time 2 minutes (120 seconds) 5 seconds 24.00 Reduced from minutes to seconds
overall schedule 6 months 4 months 1.50 2 months faster to the market
Build & Delivery Time Avg 6.43 643% FASTER DELIVERY
How much FASTER
are CloudBees Jenkins users?
6x FASTER

Cloud bees and forester open source is not enough

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (16)

Semelhante a Cloud bees and forester open source is not enough

Semelhante a Cloud bees and forester open source is not enough (20)

Mais de Jules Pierre-Louis

Mais de Jules Pierre-Louis (11)

Último

Último (20)

Cloud bees and forester open source is not enough