The document discusses Pitney Bowes' journey from manual deployment on data centers to container-based continuous delivery on AWS. It outlines how they automated their CI/CD pipeline using infrastructure as code and containerization to improve developer productivity, elasticity, and reproducibility. Their solution uses Jenkins as the central pipeline orchestrator to discover, build, test, and deploy code changes. This has helped accelerate development and delivery while enabling a DevOps culture.

1. Our journey from manual deployment on
Data center to container based CD on
AWS
Meital Morida Cohen & Genady Kofman

2. Who we are
, an Israeli start-up acquired in 2015 by Pitney Bowes.
CompleteTM Cross-Border is a scalable, end to end global ecommerce
solution that can handle all facets of enterprise retail cross-border expansion.
Pitney Bowes is a global technology company offering innovative
products and solutions that enable commerce in the areas of customer
information management, location intelligence, customer engagement,
shipping and mailing, and global ecommerce
Meital Morida Cohen
Senior Director, R&D
Genady Kofman
Architect, R&D

3. Our Agile Practices
Advanced and established agile practices
Kanban – Delivery on demand
Minimum planning and estimations
Focus on delivery of business value
Continuous Integration
Inherent within our SDLC, based on the following principles:
Fast Feedback
High Coverage

4. Why we started this journey
4
commit build test deliver
Instant 1-3 Days Days/Weeks Weeks/Months
Dependency!
Someone
needs to create a job
Dependency!
Someone
needs to provision
resources
Dependency!
CM/Resources/Handover

5. A lot to solve
Developer productivity
Elasticity
End To End Ownership
Reproducible environments
Common platform
High availability and resilience

6. Our Solution
6
A new platform that took the dependencies away
Automate CI pipeline discovery & creation
Automate environment provisioning
Automated Delivery
commit build test deliver
Instant Minutes Minutes

7. Innovation made the difference!
Cloud based solution
Infrastructure as a code
Fully reproducible
Elasticity
High Availability
Containerized infrastructure/application tier
Layered Docker Images
Jenkins Single pipeline
Scriptable pipeline, effectively making jobs definitions part of the application code
Convention based
ECS as Cluster management
Pets vs. Cattle
Auto scaling/ Auto healing

8. A new way to run software

9. A new development and delivery approach
Jenkins at the center of full software development lifecycle
Scans organization VCS to discover new projects/branches. Jobs are created for
repositories that include Jenkins pipeline scripts
All projects follow same convention: each repo covers full lifecycle, from build to deployment
It includes: Jenkinsfile (CD pipeline definition), Build scripts, Dockerfile, Deployment scripts
PB abstraction of ECS service to simplify and generalize deployment, using internal tool
ECS Tools – internal tool to save the complexity of ECS cluster

10. Jenkins Pipeline

11. Jenkins Pipeline

12. Where we are today
Business Value
Fully implement a DevOps Culture
Accelerate Development and Deployment to be more rapid ,frequent and reliable
Innovation within the teams
Architecture Flexibility - shift to Micro Services
Still ahead…
Complete reproducible environment, including DB and management tiers
Handover process
Cloud vendor independence

13. What we’ve learned
Executive backing - time and money
Resource Allocation – hiring dedicated strong people
R&D Skills – training engineers to mitigate the gap of Knowledge
Supporting organizational structure - Dev/Ops/Tech-Support
Standardizing company wide – “spreading” the platform among other
groups in the organization

14. Meital Morida Cohen
Senior Director, R&D
Meital.moridacohen@pb.com
Genady Kofman
Architect, R&D
Genady.kofman@pb.com