DevOps and
Continuous Delivery
Reference Architectures
Derek E. Weeks
VP and DevOps Advocate
Sonatype
2016
Common Elements of the Software Supply Chain
According to Cisco
Link to Presentation: Enabling DevOps
http://bit.ly/25i0RQF
According to PayPal
According to BARCLAYS
Source: http://bit.ly/244G39w
According to Adobe
Link to Presentation: Master Chef Class
http://bit.ly/1sN6o0u
57 sessions. 15 Time Zones. 15 Hours. Nov 15. Register for Free @ www.AllDayDevOps.com
According to IBM
Source: http://ibm.co/22maoB3
According to IBM
Link to Blog: DevOps Best Practice
http://ibm.co/27QQq5i
According to Cloudbees
Link to Presentation: Continuous Delivery
http://bit.ly/1YSreFu
According to US Patent & Trade Office
(USPTO)
Link to Presentation: DevOps and American Innovation
http://bit.ly/1qF8qxS
According to Rundeck
Link to Blog: What is DevOps
http://bit.ly/1sxSm2g
According to Rundeck
Link to Presentation: Rundeck + Nexus
http://bit.ly/1WKSR5B
According to Coveros
Link to Presentation: Overcoming problems
http://bit.ly/27QQNNv
According to Xebia
Link to Presentation: Journée DevOps
http://bit.ly/1XNMTAp
Nexus at Alter Way
Link to Presentation: Agnostic Continuous Delivery
http://bit.ly/1U9tHKu
According to Boxupp
Link to Blog: A DevOps Perspective
http://bit.ly/27QQBxM
According to bogotobogo
Source: http://bit.ly/1Tv0305
According to codecentric
Source: DevOps & Security
http://bit.ly/1WNJvqh
Continuous Integration Platform Using Docker Cont...
According to SimplifyOps
Source: DevOps & Security
http://bit.ly/1WNJvqh
According to eXo Software
Link to Presentation: eXo Software Factory Overview
http://bit.ly/1Tzd3DU
According to ImmobilienScout24
Link to Presentation: Be Fast or Stay Behind
http://bit.ly/20rGp9c
According to IHTSDO
Link to Blog: IHTSDO DevOps
http://bit.ly/1WKTGLP
According to CA Technologies
Link to: What are the Cool Kids Doing
http://bit.ly/27QQFxh
According to atSistemas
Link to Presentation: Presentación Integración
http://bit.ly/20rGSIr
According to CollabNet
Link to Presentation: Linking Upstream & Downstream
http://bit.ly/1WKUxMv
According to Hypoport AG
Link to Blog: Continuous Deployment
http://bit.ly/1U9vcs9 /
According to BEKK
Link to Presentation: Continuous Delivery
http://bit.ly/244K51A
According to Xebia
Link to Presentation: Continuous Delivery Workshop
http://bit.ly/1sxU6IH
According to ClinkerHQ
Link to Blog: http://blog.clinkerhq.com
According to Zanox
Link to Presentation: Continuous Delivery
http://bit.ly/1Rl0eZk
According to Riverside I/O
Link to Blog: Our Developer Toolchain
http://bit.ly/1TrzfTx
According to Dynatrace
Source: http://bit.ly/1Rl0dVs
According to Stefan Norberg
Source: http://bit.ly/1Tv2eR6 /
Nexus at Morpho
Source: http://bit.ly/1VfOVJ1
According to Morpho
Source: http://bit.ly/1VfOVJ1
According to OPENSHIFT
Source: http://bit.ly/1NHwD1C
According to akquinet
Link to Blog: Jumping into Continuous Delivery
http://bit.ly/25i7tyx
According to OCTO
Link to Blog: Continuous Delivery
http://bit.ly/1U7bIBn
According to OCTO
Link to Blog: Continuous Delivery
http://bit.ly/1U7bIBn
According to OCTO
Link to Blog: Continuous Delivery
http://bit.ly/1U7bIBn
According to Jordi Cuenca-Aubets
Link to Blog: Free Continuous Integration
http://bit.ly/1U9weEs
According to Open Sourcerers
Link to Blog: Continuous Delivery using PaaS
http://bit.ly/1WNMIq0
According to Michael Rumpf
Link to Blog: Integrating Jenkins, SonarQube, and Nexus
http://bit.ly/20rLf6u
According to Cardlife
Link to Blog: How I use Rundeck
http://bit.ly/25i8AhP
According to Paolo Antinori, RedHat
Link to Blog: Continuous Integration
http://bit.ly/1sxX6ok
According to Atlassian
Link to Presentation: Puppet Camp Sydney
http://bit.ly/1VfPgLL
According to Continuous Delivery Ltd
Link to Presentation: The Rationale for Continuous Delivery
http://bit.ly/1WdmsVa
According to CollabNet
Source: http://bit.ly/1s5i8ea
According to Nhan Ngo
Source: http://continuousdelivery.com
According to Nhan Ngo
Source: http://continuousdelivery.com
According to Nhan Ngo
Source: http://continuousdelivery.com
According to Nhan Ngo
Source: http://continuousdelivery.com
According to WS02
Source: http://bit.ly/1WdmNaC
According to CodeCentric
Source: http://bit.ly/20rNMO0
According to WS02
Source: http://bit.ly/1TzgWZM
According to Momentum SI
Source: http://bit.ly/1U9xSG9
According to Goobbe
Source: http://bit.ly/1TGH46f
According to IBM
Source: http://ibm.co/27QRarp
According to IBM
Source: http://ibm.co/22mhKV2
According to IBM
Source: http://bit.ly/1Tzhsa6
According to IBM
Source: http://bit.ly/1YSETfS
According to OZsofts
Source: http://bit.ly/22mhLZc
According to MaestroDev
Source: http://bit.ly/1U7cr5D
According to The Open Group
Source: http://bit.ly/1XsbMRP
According to AgileTrick
Source: http://bit.ly/27QR6rC
According to DevOps by Design
Source: http://bit.ly/1U9yXOd
According to HP
Source: http://bit.ly/1TrFgQg
According to Eljto
Source: http://bit.ly/20rQp2p
According to DATAPIPE
Source: http://bit.ly/1sNcH4f
According to Spirent
Source: http://bit.ly/1TGJkdH
According to Always Agile
Source: http://bit.ly/27QRtCn
According to Assembla
Source: http://bit.ly/1TrGawb
According to Girikon
Source: http://bit.ly/20rS1ZV
According to Bartholomeus
Source: http://bit.ly/244Nxcs
57 sessions. 15 Time Zones. 15 Hours. Nov 15. Register for Free @ www.AllDayDevOps.com
DevOps and Continuous Delivery Reference Architectures (including Nexus and other popular tools)
Upcoming SlideShare
Loading in …5
×

DevOps and Continuous Delivery Reference Architectures (including Nexus and other popular tools)

99,925 views

Published on

There are numerous examples of DevOps and Continuous Delivery reference architectures available, and each of them vary in levels of detail, tools highlighted, and processes followed. Yet, there is a constant theme among the tool sets: Jenkins, Maven, Sonatype Nexus, Subversion, Git, Docker, Puppet/Chef, Rundeck, ServiceNow, and Sonar seem to show up time and again.

Published in: Technology
11 Comments
340 Likes
Statistics
Notes
  • Njce! Thanks for sharing.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hey, did you see we just added the DevOps and continuous delivery toolchain from Barclays
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Just added USPTO
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Just added new reference architectures from PayPal and Riverside I/O
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • I am hosting a panel discussion on Oct 1, 2015 with Dave Farley (co-author of Continuous Delivery), Brian Dawson (DevOps Evangelist at Cloudbees) and Curtis Yanko (former DevOps Architect at Cigna) to discuss lessons learned from these Reference Architectures. They will also discuss their experience from the front lines of DevOps and Continuous Delivery deployments. You can find the webinar RSVP page at: http://go.sonatype.com/Devops_CD_Reference_Architecture_Webinar?s2=sonatypedotcomHomepage
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
99,925
On SlideShare
0
From Embeds
0
Number of Embeds
23,143
Actions
Shares
0
Downloads
4,967
Comments
11
Likes
340
Embeds 0
No embeds

No notes for slide
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow

  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Last year, we jump-started thousands of DevOps journeys.  And we  validated many more.  We did this by publishing 31 DevOps and Continuous Delivery reference architectures. These reference sheets have now been viewed more than 70,000 times.  Some are simple, some complex.  But all from the real world.  
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow

  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow

  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow

  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow

  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow

  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow

  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow
  • Last year, we jump-started thousands of DevOps journeys.  And we  validated many more.  We did this by publishing 31 DevOps and Continuous Delivery reference architectures. These reference sheets have now been viewed more than 70,000 times.  Some are simple, some complex.  But all from the real world.  
  • DevOps and Continuous Delivery Reference Architectures (including Nexus and other popular tools)

    1. 1. DevOps and Continuous Delivery Reference Architectures Derek E. Weeks VP and DevOps Advocate Sonatype 2016
    2. 2. Common Elements of the Software Supply Chain
    3. 3. According to Cisco Link to Presentation: Enabling DevOps http://bit.ly/25i0RQF
    4. 4. According to PayPal
    5. 5. According to BARCLAYS Source: http://bit.ly/244G39w
    6. 6. According to Adobe Link to Presentation: Master Chef Class http://bit.ly/1sN6o0u
    7. 7. 57 sessions. 15 Time Zones. 15 Hours. Nov 15. Register for Free @ www.AllDayDevOps.com
    8. 8. According to IBM Source: http://ibm.co/22maoB3
    9. 9. According to IBM Link to Blog: DevOps Best Practice http://ibm.co/27QQq5i
    10. 10. According to Cloudbees Link to Presentation: Continuous Delivery http://bit.ly/1YSreFu
    11. 11. According to US Patent & Trade Office (USPTO) Link to Presentation: DevOps and American Innovation http://bit.ly/1qF8qxS
    12. 12. According to Rundeck Link to Blog: What is DevOps http://bit.ly/1sxSm2g
    13. 13. According to Rundeck Link to Presentation: Rundeck + Nexus http://bit.ly/1WKSR5B
    14. 14. According to Coveros Link to Presentation: Overcoming problems http://bit.ly/27QQNNv
    15. 15. According to Xebia Link to Presentation: Journée DevOps http://bit.ly/1XNMTAp
    16. 16. Nexus at Alter Way Link to Presentation: Agnostic Continuous Delivery http://bit.ly/1U9tHKu
    17. 17. According to Boxupp Link to Blog: A DevOps Perspective http://bit.ly/27QQBxM
    18. 18. According to bogotobogo Source: http://bit.ly/1Tv0305
    19. 19. According to codecentric Source: DevOps & Security http://bit.ly/1WNJvqh Continuous Integration Platform Using Docker Containers: Jenkins, SonarQube, Nexus, GitLab
    20. 20. According to SimplifyOps Source: DevOps & Security http://bit.ly/1WNJvqh
    21. 21. According to eXo Software Link to Presentation: eXo Software Factory Overview http://bit.ly/1Tzd3DU
    22. 22. According to ImmobilienScout24 Link to Presentation: Be Fast or Stay Behind http://bit.ly/20rGp9c
    23. 23. According to IHTSDO Link to Blog: IHTSDO DevOps http://bit.ly/1WKTGLP
    24. 24. According to CA Technologies Link to: What are the Cool Kids Doing http://bit.ly/27QQFxh
    25. 25. According to atSistemas Link to Presentation: Presentación Integración http://bit.ly/20rGSIr
    26. 26. According to CollabNet Link to Presentation: Linking Upstream & Downstream http://bit.ly/1WKUxMv
    27. 27. According to Hypoport AG Link to Blog: Continuous Deployment http://bit.ly/1U9vcs9 /
    28. 28. According to BEKK Link to Presentation: Continuous Delivery http://bit.ly/244K51A
    29. 29. According to Xebia Link to Presentation: Continuous Delivery Workshop http://bit.ly/1sxU6IH
    30. 30. According to ClinkerHQ Link to Blog: http://blog.clinkerhq.com
    31. 31. According to Zanox Link to Presentation: Continuous Delivery http://bit.ly/1Rl0eZk
    32. 32. According to Riverside I/O Link to Blog: Our Developer Toolchain http://bit.ly/1TrzfTx
    33. 33. According to Dynatrace Source: http://bit.ly/1Rl0dVs
    34. 34. According to Stefan Norberg Source: http://bit.ly/1Tv2eR6 /
    35. 35. Nexus at Morpho Source: http://bit.ly/1VfOVJ1
    36. 36. According to Morpho Source: http://bit.ly/1VfOVJ1
    37. 37. According to OPENSHIFT Source: http://bit.ly/1NHwD1C
    38. 38. According to akquinet Link to Blog: Jumping into Continuous Delivery http://bit.ly/25i7tyx
    39. 39. According to OCTO Link to Blog: Continuous Delivery http://bit.ly/1U7bIBn
    40. 40. According to OCTO Link to Blog: Continuous Delivery http://bit.ly/1U7bIBn
    41. 41. According to OCTO Link to Blog: Continuous Delivery http://bit.ly/1U7bIBn
    42. 42. According to Jordi Cuenca-Aubets Link to Blog: Free Continuous Integration http://bit.ly/1U9weEs
    43. 43. According to Open Sourcerers Link to Blog: Continuous Delivery using PaaS http://bit.ly/1WNMIq0
    44. 44. According to Michael Rumpf Link to Blog: Integrating Jenkins, SonarQube, and Nexus http://bit.ly/20rLf6u
    45. 45. According to Cardlife Link to Blog: How I use Rundeck http://bit.ly/25i8AhP
    46. 46. According to Paolo Antinori, RedHat Link to Blog: Continuous Integration http://bit.ly/1sxX6ok
    47. 47. According to Atlassian Link to Presentation: Puppet Camp Sydney http://bit.ly/1VfPgLL
    48. 48. According to Continuous Delivery Ltd Link to Presentation: The Rationale for Continuous Delivery http://bit.ly/1WdmsVa
    49. 49. According to CollabNet Source: http://bit.ly/1s5i8ea
    50. 50. According to Nhan Ngo Source: http://continuousdelivery.com
    51. 51. According to Nhan Ngo Source: http://continuousdelivery.com
    52. 52. According to Nhan Ngo Source: http://continuousdelivery.com
    53. 53. According to Nhan Ngo Source: http://continuousdelivery.com
    54. 54. According to WS02 Source: http://bit.ly/1WdmNaC
    55. 55. According to CodeCentric Source: http://bit.ly/20rNMO0
    56. 56. According to WS02 Source: http://bit.ly/1TzgWZM
    57. 57. According to Momentum SI Source: http://bit.ly/1U9xSG9
    58. 58. According to Goobbe Source: http://bit.ly/1TGH46f
    59. 59. According to IBM Source: http://ibm.co/27QRarp
    60. 60. According to IBM Source: http://ibm.co/22mhKV2
    61. 61. According to IBM Source: http://bit.ly/1Tzhsa6
    62. 62. According to IBM Source: http://bit.ly/1YSETfS
    63. 63. According to OZsofts Source: http://bit.ly/22mhLZc
    64. 64. According to MaestroDev Source: http://bit.ly/1U7cr5D
    65. 65. According to The Open Group Source: http://bit.ly/1XsbMRP
    66. 66. According to AgileTrick Source: http://bit.ly/27QR6rC
    67. 67. According to DevOps by Design Source: http://bit.ly/1U9yXOd
    68. 68. According to HP Source: http://bit.ly/1TrFgQg
    69. 69. According to Eljto Source: http://bit.ly/20rQp2p
    70. 70. According to DATAPIPE Source: http://bit.ly/1sNcH4f
    71. 71. According to Spirent Source: http://bit.ly/1TGJkdH
    72. 72. According to Always Agile Source: http://bit.ly/27QRtCn
    73. 73. According to Assembla Source: http://bit.ly/1TrGawb
    74. 74. According to Girikon Source: http://bit.ly/20rS1ZV
    75. 75. According to Bartholomeus Source: http://bit.ly/244Nxcs
    76. 76. 57 sessions. 15 Time Zones. 15 Hours. Nov 15. Register for Free @ www.AllDayDevOps.com

    ×