Designing Autodesk’s Future Today

CI/CD for the Whole Product

George Swan
Director, Engineering Solutions
Autodesk

george.swan@autodesk.com
WHY DID AUTODESK ADOPT DEVOPS (CI/CD)?

Subscription Licensing

Cloud Platform Company

Collaboration

Unified Solution
SUCCESS METRICS
DORA Metrics Social Development

Adoption (Tools, Pipeline, Best Practices) Inner-source Content

Open-Source Contribution

Reference: Accelerate – State of DevOps 2018 Reference: Hubble

SOUND FAMILIAR?

200 products: Desktop, Web, Mobile

Yearly Global launch

Limited Sharing. Lots of Duplication

Last-generation Tools
REACH HIGHER

Application vs. Software

Continuously Deliver Applications

Desktop, Web & Mobile

OUR THREE YEAR JOURNEY

Executive Buy-in

Software CI/CD Pipeline

Inner-Sourcing Components

Documentation Pipeline

Localization Pipeline
STEP 1: MANAGEMENT SUPPORT

Fortuitous Timing

Executive Desire

Engineering Desire

Transformational Leadership
STEP 2: NEW DEVELOPMENT PLATFORM
4000 Users 2000 Users 8000 Users

16,000 Repos
53,000 Builds/week 7000 Channels
18M Git commands/day

1.5M Artifacts 2.5M Issues/year

1.8M Downloads/day
400k pages
SOFTWARE CI/CD PIPELINE

Test coverage CI/CD Best Practices

Source
Desktop CD

Build Test Publish Image Cloud CD

Binaries Mobile CD
CI/CD BEST PRACTICES

Culture & Mindset

Loosely Coupled

Automation & Version Control

Continuous Integration

Shift-left & Quality-as-code

Reference: Accelerate – State of DevOps 2017

Lean Product Development
LESSONS LEARNED

Transformational Leadership

Tiered Adoption

White-Glove vs. Self-Serve

Success is 70%

Evangelize, Market & Nag

High Support Costs

STEP 3: COMPONENT GOVERNANCE
Manual Approval and Validation

Different Copies

Ingestion Workflow

Unified Generation & Consumption

INNER-SOURCED COMPONENTS

New Component Workflow

Source
GitHub Repo
Inner-Source
Best Practices
CI/D
Inner-Sourced

OSS CI/CD Binaries

Unified Consumption

Open Source Contribution Parents

Same for 3rd party & Internal Components

LESSONS LEARNED

Local Cost vs. Global Gain

Ownership is Hard

Dependency Breaking Hard at Scale

Unification is Valuable
STEP 4: APPLICATION DOCUMENTATION

API documentation

Application Content:
On-line Help
What’s New
Update Notifications

Translated to 12 Languages
 PRIOR DOCUMENTATION SOLUTION

AKN
Source

Highly customized by ADSK

On-line
Product Help

Off-line Product Help

DOCUMENTATION PIPELINE

CI/CD Best Practices

• Markdown Syntax Checker

• Valid links
• Unused resources

Source Build Test Publish Image CD

Markdown

Magic Green Button

LESSONS LEARNED
Docs Stored Alongside Software

DORA Best Practices Apply

Anyone can Edit

Developers Understand Pull Requests

Keen Interest in Migrating

STEP 5: LOCALIZATION
12+ Languages

Translate 1.4 billion words per year

Typical Solutions:
English only
Localization Service Providers (LSP)

Anti-pattern to CI/CD
TRANSLATION WORKFLOW
Branch abc (docs, s/w)
Source

4. Merge
abc-localize Translation
Repository
Pull
3.
Request 2. 7.

1.

5. 6. Localization
Auto-Translation Service
• Statistical (Moses) Provider
• Neural (openNMT) New
Segments
LOCALIZATION PIPELINE

Localization
Globalizer (Static Analysis)

Build Test Publish CD

Source Image

• Software
• Documentation Build Test Publish CD
LESSONS LEARNED

Localization can be Continuous

Large Investment in Auto-Translation

Neural Translation Technology

APPLICATION PIPELINE

CI/CD Best Practices

Localization CI

Desktop CD

Source Doc CI Cloud CD

Inner-Source Images
Best Practices S/w CI Mobile CD

OSS, etc. CI/CD Binaries Doc CD

Parents
NEW BLISS

Product CI/CD Exists

Teams Actively On-boarding

Culturally, Night vs. Day

FINAL THOUGHTS

Maximize Your CD Performance

Reach Higher on CD

Chart your new course to Success

Thank You Supporters
 Designing Autodesk’s Future Today
CI/CD for the Whole Product
George Swan
Director, Engineering Solutions
Autodesk

george.swan@Autodesk.com

All Day DevOps October 17, 2018