Smart Decoding is a content series focused on breaking down trends and concepts in the banking and technology industries and highlight how the Chase Product & Experience and Technology team designs, builds, develops and power up the products they create for our customers and employees use.

Serving nearly 80 million customers and nearly 6 million small businesses in the U.S., Chase’s ability to deliver quality customer experiences with our products and technology relies on stability, quality and speed. Our size and scale are assets to Chase employees and customers, but they can also present challenges.

Why it matters: Writing code is harder than it was 20 years ago since technology and capabilities have grown. Plus, dependencies on systems that were developed decades ago make launching code into production even more difficult. Our solution?

TrueCD, or True Continuous Delivery, is Chase’s practice of Continuous Integration Continuous Delivery (CICD). It is a set of automated practices for testing across applications with the goal of releasing code changes in less than one hour with confidence and quality.

 

Engineers adopting TrueCD accomplish this by automating:

  1. Onboarding to Chase’s enterprise toolchain
  2. Unit testing
  3. Contract testing
  4. Component testing
  5. Acceptance testing
  6. End-to-end testing
  7. Performance testing
  8. Security testing
  9. Resiliency testing
  10. Blue/green deployment
  11. Production validation
  12. Automated rollback

All sit within an approved toolchain to help with efficiency, compliance and required standards.

The illustration shows a horizontal figure eight-like cycle with a starting point titled Onboarding to Chase’s enterprise toolchain, with an arrow pointing to Unit Testing, followed Contract Testing, Component Testing, Acceptance Testing, End-to-End Testing, Performance Testing, Security Testing, Resilience Testing, Blue/Green Deploy, Production Validation, Automated Rollback, and back to Unit Testing.

What success looks like: Increase in developer productivity. Now we can spend time tackling big problems and direct our brain power to innovative thinking instead of rote work that could have manual error due to our size and scale. Testing is critical for an amazing customer experience at launch. So, let’s set it and forget it.  

How we’ll get there:

  • Having development teams continue to adopt all 12 steps as they build code.
  • Sharing our achievements to help win over team members since this requires a shift in how we build code and will take effort in the beginning—like our team that cut production time from six sprints to four by implementing the steps.
  • Ensuring all new code and features use TrueCD’s practices.

Go deeper: Check out TrueCD at Chase Boosts Mobile Team Productivity to discover in-depth how Chase is using TrueCD to empower engineers, reduce toil and improve software quality, and learn more about how Chase technology teams are using Continuous Integration Continuous Delivery (CICD) across the organization, including for new mobile app releases and updates.

Like what you’re reading? Check out all our opportunities in tech here.

JPMorgan Chase is an Equal Opportunity Employer, including Disability/Veterans

For Informational/Educational Purposes Only: The opinions expressed in this article may differ from other employees and departments of JPMorgan Chase & Co. Opinions and strategies described may not be appropriate for everyone and are not intended as specific advice/recommendation for any individual. You should carefully consider your needs and objectives before making any decisions and consult the appropriate professional(s). Outlooks and past performance are not guarantees of future results.

Any mentions of third-party trademarks, brand names, products and services are for referential purposes only and any mention thereof is not meant to imply any sponsorship, endorsement, or affiliation.