As change agents for data integration, keeping pace and adapting quickly to today’s fast and fluid digital customer compelled Axway’s globally distributed R&D team to move their DevOps to the cloud. See how they leveraged Gitlab and other value stream tooling to drive their digital transformation from an on-premise Internet Service Provider to a Cloud Provider. Follow their Continuous Integration to Continuous Security and Delivery journey to learn how they: - Achieve 26x faster release cycles and 100% developer adoption - Enable collaboration for multiple teams across continents and timezones - Simplified their source code repository administration - Implemented world-class integrations and flexible API-enabled, seamless workflows

1. 1#GitLabCommit
Axway’s Journey To The Cloud
Vince Stammegna,
Sr Director Engineering
Eric Labourdette,
VP Cloud Operations

2. 2#GitLabCommit
Enabling your digital business by connecting people, processes, and things
while governing data flows throughout your ecosystem
283.4M€
2018 REVENUE
43% in US
29% in France
23% in EMEA
5% in Asia
Listed on Euronext (AXW.PA)
17.2%
CLOUD GROWTH
(H1 2019)
1850
EMPLOYEES
across 19
countries
Global HQ, Phoenix AZ
2
11000
CUSTOMERS
100+ patents
65B API Calls

3. 3#GitLabCommit
Problem Statement

4. 4#GitLabCommit
Tools Transformation
● Transitioned in 2016 from SVN/VersionOne to Gitlab/JIRA/Confluence
● Tools are a support to your transformation, not a driver; however, they are key to success.
○ Open policy to all (license for all with read access)
○ Same tooling to foster collaboration (all source code in Gitlab, all backlog in JIRA)
○ Central and integrated tool ecosystem (ease developer’s life)

5. 5#GitLabCommit
Organization Transformation
New expectations for managers
● No longer review, validate, and decide everything
● No more assigning tasks to reach objectives
● Enable collaboration, animate groups, ensure
everyone is empowered on the team
● Provide guidance, help with connections to
other groups
New expectations for collaborators
● No more execution without understanding
● Need to understand the global target and
their contribution
● Need to take initiative to reach objectives

6. 6#GitLabCommit
R&D Jobs Transformation
SaaS,
Continuous
Delivery
From
To

7. 7#GitLabCommit
Technology Transformation
Imperative: DevOps
● Rapid, collaborative design
● Continuous integration,
testing, and delivery
● High automation
Imperative: Microservices
● Containerization
● Complete isolation
● Event-driven, serverless
Imperative: Cloud
● Support any client interface
● Run anywhere
● Pay as you go
● Consume on demand

8. 8#GitLabCommit
Culture rules them all!!

9. 9#GitLabCommit
But how do you change Culture?

10. 10#GitLabCommit
Start with Behaviors!

11. 11#GitLabCommit https://devblog.axway.com/dev-insights/keep-calms-devops-c-culture/

12. 12#GitLabCommit
Keep CALMS and Measure: How do you measure DevOps?

13. 13#GitLabCommit
How did we measure in 2019?

14. 14#GitLabCommit
Where do we want to be for 2020?

15. 15#GitLabCommit
Stages of Software Delivery Evolution - Elite Characteristics

16. 16#GitLabCommit
Automate and Empower: Self-Service
for Dev Teams
Objectives:
● Eat our own dog food
● Create common pipelines that build and deploy
images, QA them, and execute security scans
(Nessus, Twistlock, etc.)
● Defines how teams will go through the product
automation lifecycle when they control their
Jenkins
● Reuse the same pipelines and Jenkins
configuration on the builds automatically
triggered from Master

17. 17#GitLabCommit
Immutable Infra,
Images, Deployment
Tools used
throughout the CD
pipeline
CD Objectives:
• Immutable Infra,
Images, Deployment
Tools
• Common CD paths
from DEV to PROD
• Dashboard / Release
Readiness Report
CI Objectives:
• Common Local DEV
• Common CI paths for
development
• Common Image Registry
• Dashboard / Build /
Vulnerability Reports
Step 1:
DEV – Integration Tests
QA – E2E Tests
Step 2: Handoff to
TechOps / RRR / E2E
2019: SaaS CI/CD Pipelines on AWS

18. 18#GitLabCommit
Keep CALMS and Lean: How do you practice Lean?

19. 19#GitLabCommit
Keep CALMS and Share: How does your organization
Share?

20. 20#GitLabCommit
Immutable Infra,
Images, Deployment
Tools used
throughout the CD
pipeline
CD Objectives:
• Immutable Infra,
Images, Deployment
Tools
• Common CD paths
from DEV to PROD
• Dashboard / Release
Readiness Report
CI Objectives:
• Common Local DEV
• Common CI paths for Infra,
Image and Tool
development
• Common Image Registry
• Dashboard / Build /
Vulnerability Reports
Step 1:
DEV – Integration Tests
QA – E2E Tests
Step 2: Continuous
Deployment
2020: SaaS CI/CD Pipelines on AWS

21. 21#GitLabCommit
Lessons Learned
Executive sponsorship required
○ Transformation requires vigilance
Tools can support your transformation, but culture is key to success
○ Developers need faster feedback to build better products
Portfolio rationalization enables solution focus and cloud first design
○ Moved from 50 products to 4 strategic solutions and then platform
Continuous Improvement and Accountability

22. 22#GitLabCommit