Implementing Rapid and Repeatable Pipeline for an Enterprise

Enterprises and their individual feature teams are in a rush to build DevOps Pipelines with all the right reasons.

While central teams are provisioning tools to be consumed at Enterprise level, individual feature teams are focusing heavily on building pipelines instead of building and enhancing business priorities.

This results in "duplicate pipelines” solving the same problem of automation for build, test, package, infra, deploy and release using the given toolsets. - This results into duplication of efforts and redundancy.

We intend to share our approach to build a pipeline enabled to for polygot programming languages and consumption patterns supporting various areas including.

  • A single click to deploy the complete pipeline infrastructure and app pipeline
  • Support multiple cloud deployment (AWS, Azure, etc…)
  • Adoption of open source tools
  • Clustered or non-clustered infrastructure deployments

We will also emphasize on the implementation experience of the advanced Engineering practices in the area of immutable infrastructure, Chaos Engineering, blue-green/canary deployment.


Outline/Structure of the Case Study

  1. Defining the problem statement and challenges with Pipeline adoption [5 mins]
  2. The Rapid Repeatable Pipeline Approach [25 mins]
    1. Our definition of Rapid Repeatable Pipeline(RRP)?
    2. A high level solution
    3. Tools and Technology
    4. Success Criteria for Enterprise Implementation
    5. Our Learnings and Derived Outcomes
  3. Advanced Engineering areas [10 mins]
  4. Q&A [5 mins]

Learning Outcome

Through this session we intend to drive following learning outcome for the audience:

- Accelerate the DevOps journey and bring repeatability

-Improved synergy on business value outcome

-Optimization of engineering efforts

Target Audience

Architects; Tech Leads; Technologists; Product Managers; Scrum Masters;

Prerequisites for Attendees

- Basic understanding of DevOps and pipelines

- Basic knowledge of cloud deployments and DevOps tools

schedule Submitted 2 years ago

Public Feedback

    • Tobias Anderberg
      Tobias Anderberg
      Agical AB
      schedule 2 years ago
      Sold Out!
      45 Mins

      Ever wondered why some people prefer to work alone? Or why some people cringe when pair programming is mentioned? It might be that that person, like me, is an introvert. But is is really that simple? Can we really put every person in a box labeled "introvert" or "extrovert" or are we all just ambiverts?

      During this session I will talk about introverts, extroverts and everything in between.
      Drawing from almost 15 years of personal experience being an introvert on agile teams I will talk about the differences of being an extrovert
      or an introvert, how to foster an inclusive team environment, and the importance of psychological safety.
      You will hopefully leave this session better fit to help EVERYONE on your team to reach their full potential!

    • Vincent FUCHS

      Vincent FUCHS - Keeping hundreds of code repositories consistent, and staying sane !

      20 Mins

      With the move to microservices architecture, a lot of teams end up managing dozens of code repositories (vs just a couple before), and some tasks that were done quickly manually are now becoming very time consuming : consistency of the repositories, and eventually of your platform, gets impacted, making it more and more difficult to manage.

      Surely, there must be some tools existing to take care of boring tasks like finding where a given dependency is used, and upgrade it automatically (this is just an example)... Well actually, we didn't find anything, so we implemented them ourselves and made them available for everyone !

    • Gabor Devenyi

      Gabor Devenyi / Alex Sloley - The magic number is 10

      45 Mins

      Why are Agile teams supposed to be small? How big are they supposed to be? Most agilists tend to agree that a team of ten people works well.

      But what is it about the number 10 that makes it the “magic” number?

      Since the start of human evolution, people formed groups to be more effective. Whether it was the hunt for a mammoth or going to war, working in teams ensured a greater chance of success.

      There have been various researches from Dunbar’s paper through the Scrum Guide to military formations about the ideal number of people in a team.

      We’ll discuss the historical, scientific and cultural reasons why 10 seems to be the magic number of forming effective teams.

      Does the number of team members really matter? Is 10 really the magic number. You will get an answer that will help you to create effective teams with the right amount of people.

    • Vivek Ganesan

      Vivek Ganesan / Rejikrishnan Rajan - Reinventing DevOps Practices for Blockchain Applications

      90 Mins

      With the arrival of distributed applications that run on Blockchain, it is essential to rethink some of the basic aspects of DevOps. Few things that we take for granted in DevOps area are either irrelevant, impossible or too costly for blockchain applications. Join us to explore the changes that the blockchain apps bring to the DevOps arena, using a hands-on demo of a sample blockchain app.

    • Rajith Raveendranath

      Rajith Raveendranath - Blazing fast Big Data processing - High performance big data processing using Micro-services & Flow Based Programming

      Rajith Raveendranath
      Rajith Raveendranath
      Director Engineering
      schedule 2 years ago
      Sold Out!
      20 Mins
      Experience Report

      An experience share about how we achieved high performance transaction pricing with elastic scaling, for a big T in the US, using Micro-services and Flow Based Programming.

      We start with the challenges faced by the telecom operator in their All IP access network which necessitates high volume, low latency transaction processing.

      We discuss the Micro-services advantage which let us build responsive, resilient and elastic services.

      We further discuss the FBP edge, which help us manage the big data effectively and also work as an event driven framework for Micro-services

      We will have a short discussion on the software stack used.

      We conclude by sharing the results and the lessons learnt

    • Jen Krieger

      Jen Krieger - So you want to be a DevOps Engineer?

      Jen Krieger
      Jen Krieger
      Chief Agile Architect
      Red Hat
      schedule 2 years ago
      Sold Out!
      45 Mins

      You’ve worked hard, you have mastered every coding language on the planet, including COBOL. You know jenkins, travis, go, containers, puppet, chef, CFengine, nagios, github, graphite, logstash, ansible, aws, gce, vagrant, cms, cvs, abc, 123, and even a little bit of TFS. Your resume is up to date, and you are ready for your next job.

      Well, slow down there… Industry trends in engineering are showing a growing desire in companies to hire people who have proven soft skills, are good at collaborating with others, and can regularly solve the most complex problem we face today: effectively talking to our fellow humans.

      Please join Jen for a self-effacing and situationally humorous conversation about the journey of becoming more comfortable with collaboration, open communication and reaching through “the wall.”

      Topics will include:

      • “Collaborate or Die” survival skills
      • The dreaded “soft skills” and how to become comfortable with them
      • What to do in common situations all engineers face
      • How to convince others that your idea is the right idea
      • How do you get the time you need to get your work done