1.
Continuous Integration and
Delivery at Shapeways
Matt Boyle NordicAPIs Platform Summit
Stockholm, Sweden25 October 2016

2.
What is Shapeways?
The worlds largest 3d printing service
and marketplace
Marketplace, service hub, and
community hosted at Shapeways.com
REST API provided at
api.shapeways.com

3.
Why CI/CD?
Idea
Exploration
Definition
Execution
Release
Evaluation
Consider the SDLC
…except this one
All stages represent active, valuable
work by software team members.

4.
Releasing Software Starts Easy
Everything
Working?

5.
Releasing Software Gets Harder
Git pull
Build
FrontEnd?
Manage
Symlinks?
Bounce
Memcache?
Restart
Apache?

6.
Releasing Software Gets REALLY hard
Build Artifact
Run tests
Deploy to
multiple
datacenters
Intra-DC
deployment to
servers
Manage artifacts
on server
Rotate through
load balancer
Generate
documentation
Restart services
Detect
regressions
Monitor for
Breakages
Deployments like this take time and
resources
If you don’t automate, you’ll spend as
much time running deployments as you do
writing code

7.
The Shapeways CI Story

8.
In The Beginning…
60 minute deployments No API documentation Frustrating Manual Testing

9.
Baby Steps
Continuous Integration
with Jenkins
Integration + Functional
Testing with Selenium
New tests required to
ship features

10.
Pro’ing up - Jenkins
Active-Active Jenkins instances – one per
datacenter
Use Jenkins API for remote execution of
deployments and test jobs
Flow-based deployment using Jenkins
Pipeline DDL

11.
Pro’ing up - Coyote Framework
In-house FOSS testing framework for
integration and functional testing
Thoughtfully developed testing infrastructure
to ensure consistent, reliable, and
maintainable tests
Two-level API testing: contract enforcement
and functional flow

12.
Pro’ing up - ACME
In-house developed test management
application
Schedule test runs on-demand for developers
Test analysis and intelligence

13.
Pro’ing up - ChatOps via Hubot
GitHub-developed extensible chat bot written
in CoffeeScript
Manage deployments, development/QA
infrastructure, permission management
Acts as interface between our different tools:
jenkins, coyote, acme, slack

14.
Looking Ahead – Staged Rollouts
Present deployment is fast but requires us to
be all-in on new code
Ability to use infrastructure for new feature A/B
testing rather than user groups
Increased deployment time, but faster
recovery should something go wrong

15.
Looking Ahead - Swagger for all APIs, int+ext
Easier documentation generation
Client generation/update for multiple
languages
Source of truth for service-based applications
– contract enforcement, test generation

16.
Looking Ahead - Improved Testing Tooling
Generate testing profiles based on changes
made in codebase
Code coverage for functional testing via URL
mapping
Performance and capacity measurement
based on previous test runs and environments