DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. DevOps and CI/CD
  4. Continuous Discussions Podcast, Episode 89: The DevOps Toolchain [Podcast]

Continuous Discussions Podcast, Episode 89: The DevOps Toolchain [Podcast]

Tools must be able to integrate with each other and provide insight into the entire process. Check out the latest Continuous Discussions podcast for insights like this.

Tom Smith user avatar by
Tom Smith
CORE ·
Jul. 20, 18 · Interview
Like (2)
Save
Tweet
Share
5.35K Views

Join the DZone community and get the full member experience.

Join For Free

i just took part in a great podcast hosted by electric cloud in partnership with dzone with a round-table discussion on the importance of a healthy devops toolchain .

participants in the podcast included:

prashant mohan prashant mohan, product manager for smartbear’s software testing tools. @prashz91

lee atchison lee atchison, senior director, strategic architecture at new relic. @leeatchison

ian buchanan ian buchanan, developer advocate at atlassian. @devpartisan

mark miller mark miller, devops evangelist at sonatype. @eusp | alldaydevops.com

ravi gadhia ravi gadhia, senior solutions engineer at github.

our hosts were:

image title anders wallgren, cto at electric cloud. @anders_wallgren

and

image title

sam fell, v.p. marketing at electric cloud. @samueldfell

key takeaways include:

the devops toolchain as a value stream

it's important to look at the entire value stream looking at the lead time ladder and identifying bottlenecks where automation will add the greatest value.

you need to be able to see upstream and downstream to ensure you are adding value and not duplicating effort. have a single set of integrated tools giving you vision into how the entire process is working.

think about what the code is seeing and how it's being affected.

use tools to align people and teams

given that the greatest challenge to implementing a devops methodology is culture, it's important for every member of the team to have visibility and access to metrics for every link in the toolchain.

devops is enabling cultural transformation while security overlays the entire process.

value stream mapping is the biggest hurdle companies need to get over. once you understand the whole process and the outcomes you are trying to achieve every member of the team is able to see where they are contributing and where they are hindering the process.

is there one right tool?

no; however, there's a correct set of tools for every organization and you determine this by choosing the right tool for the problem you are working to solve. every tool has a purpose and it must integrate with every other tool and provide a holistic view of the process. there is value in standardization; however, be aware that the right tool might change. as such, tools need to be able for clients to change in and out.

the tools have to work together. you cannot expect companies to "rip and replace." it's too expensive, time-consuming, and there are a lot of people to be trained on the new tool.

adapting to the changing environment

we need to be able to abstract out the details of the actual tools and focus on the outcome of the process versus the tool that's being used to achieve the outcome.

tools must integrate into a platform that's easy and intuitive for team members to use. the tools need to provide access to data and vision into the entire pipeline for audit-ability and traceability.

think holistically about the entire devops toolchain.

check out the full episode:

you can find electric cloud's write-up of the podcast here , and check out the previous episodes of continuous discussions (#c9d9) .

DevOps Podcast

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Top Three Docker Alternatives To Consider
  • Top 5 Java REST API Frameworks
  • Stream Processing vs. Batch Processing: What to Know
  • What Was the Question Again, ChatGPT?

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: