The Container Contract : Unit of Exchange for successful Delivery Pipeline


Imagine what if everything is automated , now what ?  are you done yet ?  

No , We still want our team's deliverables to be clean and unambiguous, reducing friction in our delivery pipeline , but how is this possible forever ?

Solution - Container contracts to facilitate clean deliverables between teams.

A Container contract is a clean line of separation between teams, where the Docker image is both the borderline and the unit of exchange.


At this talk, we will learn how to leverage the container technology to solve the challenges of the delivery  pipeline with Container contracts.

But Why with Docker 

1.Docker is becoming a standard for managing infrastructure using containers.

2.The product,testing or Operational code and its infrastructure are growing at scale with more complexity, dependencies and technology diversity.


Outline/Structure of the Demonstration




Outline/structure of the Session
1.Challenges in Managing a Delivery Pipeline - 5 min

2.Container Contract and workflow - 5 min

3.How to Implement Container contracts in your Pipeline - 10 min

4.Live Demonstration of Delivery Pipeline over containers - 15 min

5.Best Practices and Patterns - 5 min

6.Questions and Answers - 5 min

Learning Outcome

You will Learn 

  • Docker, how it works and why it's important to not just ops but for everyone  
  • Docker tools to support delivery pipeline
  • Integrate container contracts into a CI pipeline
  • Examples for taking your projects ahead. 

Target Audience

Testers, Developers, SysOps and Product Managers

schedule Submitted 2 years ago

Public Feedback

comment Suggest improvements to the Speaker
  • Joel Tosi
    By Joel Tosi  ~  2 years ago
    reply Reply


    Hi Irfan,

       Do you have a link to the demo anywhere?  Is that in the video (my apologies, I have not looked at it yet - on a slow hotel wifi)




      By IRFAN AHMAD  ~  2 years ago
      reply Reply

      Hi Joel, 

      Yes 2 of the demo's are there in the presentation but they are only concerned with the testing stage , will add another demo which will have all stages in delivery pipeline .

  • Leena S N
    By Leena S N  ~  2 years ago
    reply Reply

    Hi Irfan,


    Can you give more details on the following as it is not very clear:

    - How Container Contracts solves the unambiguity among the team for  deliverables? 

    - How does it help to create a Delivery Pipeline?



      By IRFAN AHMAD  ~  2 years ago
      reply Reply

      Hi Leena ,

      Below are the responses

      How Container Contracts solves the unambiguity among the team for  deliverables? 

      Hi, Few of the below operational efficiencies result from having this contract (single reference touch-point).
      1.Upgrades become the responsibility of the team delivering the change.
      2.Bug reproduction becomes much easier, as all teams are able to describe and reproduce issues from a known starting point.
      3.state is always managed by those making the change ,instead of the separate release team.
      4.follow same common steps irrespective of underlying environments or technology stack.

      All these benefits to help to reduce the communications overhead and allow teams to get on with their jobs.
      and help the team to improve their agility and delivery quality.


      - How does it help to create a Delivery Pipeline?

      Nothing new in delivery Pipeline ,it will have same stages (Eg Commit,Build,Test,Deploy)
      but only the unit of exchange changes to a docker container(code+config) instead of code in between these stages.