SlideShare a Scribd company logo
Continuous Integration
for Heterogeneous
Environments

Nils Hofmeister, 11.09.2011
PHP Unconference
Hello world!

• Nils Hofmeister
• 5+ Years experience in realtime 3D / C++
• 2+ Years experience in web-based games (php, javascript, Java, C++, C#)
• Lead Integration Architect @Bigpoint, Hamburg – “the SVN guy” ;)
2
Agenda

• What is continuous integration?
• Why do you want continuous integration for your project?
• How do we implement continuous integration at Bigpoint?

• What are our next steps?

3
What is continuous
integration?

4
What is continuous integration?
The gossip
• A way to automize certain tasks, e.g.
• code validation
• build automation
• packaging of products

• A system of cooperating hardware- and software components , e.g.
• Source code management system (SCM)
• Staging system + production servers
• Build cluster with all kinds of compilers and frameworks on it

The idea behind this is much more important, so we do the technical stuff later.

5
What is continuous integration?
The idea
• Not brand-new: First known example: IBM OS/360, early 60s
• Current ideas and drivers closely related to agile movement and Extreme
Programming
• Martin Fowler says:
•
•
•
•
•
•
•

software development practice
integrate *…+ frequently
multiple integrations per day
verified by an automated build
detect integration errors
significantly reduced integration problems
develop cohesive software more rapidly

Martin Fowler on Continuous Integration - 2006 version
Original article – 2000
6
What is continuous integration?
The philosophy
Jez Humble says in "Continuous Delivery":
•
•
•
•
•
•
•
•

Create a repeatable, reliable process [...]
Automate almost everything
Keep everything in version control
If it hurts, do it more freqeuntly and bring the pain forward
Build quality in
Done means released
Everybody is responsible for the delivery process
Continuous improvement

“If something hurts, do it more often”
7
What is continuous integration?
The attitude

• Accept that CI is a standard tool. Just as compilers, SCMs or documentation are
• Understand that failing builds must have highest priority - always!
• Keep in mind that errors happen anyway. CI only makes them visible
immediately and reliably.
8
Why do you want continuous
integration for your
project?
9
Why do you want continuous integration for your project?
Reduce risks

• Defects are detected and fixed sooner
• Health of software is measurable
• Reduce assumptions (environment variables, local setup, etc)
10
Why do you want continuous integration for your project?
Reduce repetitive manual processes

• Process runs the same way every time
• The process starts automatically
• This frees resources for higher-value work
11
Why do you want continuous integration for your project?
Generate deployable software

• Product is deployable always
• Paradigm-shift from crunch time before release to "always ready to deliver"
12
Why do you want continuous integration for your project?
Better project visibility

• Supports effective decisions
• Facilitates recognizing trends
13
Why do you want continuous integration for your project?
Greater confidence in your project

• CI provides a safety net to avoid releasing flawed software
• Developers get a better feeling for impact of changes
14
How do we implement
continuous integration at
Bigpoint?
15
How do we implement continuous integration at Bigpoint?
The setting

• Websites, backend systems, clients
• PHP is one of many technologies required to assemble our games (an important one,
don’t worry ;))
16
How do we implement continuous integration at Bigpoint?
The requirements

• Per artifact:
• Check for defects
• Measure quality
• Per project:
• Assemble deliverable packages
• Deploy these
17
How do we implement continuous integration at Bigpoint?
The solution space (subjective! and there is more of course)
Microsoft Team Foundation Server
Integrates fine with Microsoft Tools. But with nothing else 
TeamCity
Well-known product by JetBrains. Feature set is fine, but no USP
that justifies to pay for it right now.

CruiseControl
The classic invented by ThoughtWorks. Now an open source
project. Delightfully old-school.
Bamboo
Quite solid, full-featured product by Atlassian. No real USP though
that justifies the high price.
Go
The current CI solution by ThoughtWorks. The theory behind it is
cool but it lacks a lot of features and configuration is no fun.
18
How do we implement continuous integration at Bigpoint?
The actual solution for us

• Hudson:
• Created by Kohsuke Kawaguchi
• "Duke's Choice Award" in 2008
• Comes from the Java world, ships with CVS/SVN, Maven, JUnit support

• Jenkins:
• Kohsuke was working for Sun till Oracle acquired Sun in 2010
• Conflict between the Hudson Core developers and Oracle => Fork in 2011

19
How do we implement continuous integration at Bigpoint?
The actual solution for us II

• Trends after fork
• Hudson => Focus on quality & stability
• Jenkins => Core developers, faster pace
• Our decision
• choose Jenkins as for us features > stability.
• to compensate we use Jenkins LTS

20
How do we implement continuous integration at Bigpoint?
The actual solution for us III

We like the Jenkins community!
(My colleague Marcelo and Kohsuke on their way to get their hands on some beer)
21
How do we implement continuous integration at Bigpoint?
Hamburg Jenkins cluster
There are more instances, but this is the biggest one…
• Setup
• 1 fileserver as master (Debian)
• 3 blades (Debian)
• 4 windows workstations

• Toolchains
•
•
•
•
•

Java
Flash/Flex
Php (+ JS, html, CSS)
Unity/Mono
C++

• Highly customized
• Home-grown housekeeping + backup
• Custom plugins / actively develop Jenkins
• All the stuff needed to deal with Kerberos…
22
How do we implement continuous integration at Bigpoint?
Hamburg Jenkins cluster II
Under the hood:
• Unity3D
• Unity/Mono + Ant

• Java
• Maven + some Ant
• Artifactory/Nexus (memo: synergies…)

• Flash
• Ant/Maven (Not sure who will win yet)

• C++
• gcc/make via Ant/Shell

• PHP/web apps
• All glory to Sebastian Bergmann – we more or less use his template…
• …plus some mods, e.g. minifiers, CDN stuff,

23
How do we implement continuous integration at Bigpoint?
Bigpoint standard game build pipeline

Behold: join plugin, downstream builds, copy artifacts, parameterized builds.
We do not do deployment from within Jenkins but have a custom deployment tool.
Interface is SVN tags.
24
How do we implement continuous integration at Bigpoint?
Bigpoint standard build pipeline II

• Oh noes, this is too slow…
• Optimize hardware
• Parallelize wherever possible
• Where not possible, decompose and create additional pipelines

• But… this is a SPOF!
•
•
•
•

Backup _everything_ automatically
Fully automized CI server setup
Find some replication/failover setup (todo)
Remember: everything the CI server does must run on your machine as well!

• Wait a minute… no more Ninja-deployment? But we need that to be agile…
• No you don’t 

25
How do we implement continuous integration at Bigpoint?
The obstacles

• The vast amount of knowledge needed
• Understanding the Bigpoint platform (the Release Engineering team is “brand new”)
• The different requirements, setup and skills of about 25 groups of stakeholders

• Linux/IT-driven platform vs. Java toolchain
• Acceptance (everyone claims to like Software Engineering, but some people seem to
have a different understanding of what that is  )

We can handle much of this very well by now.
Our biggest problem remaining:
• Technical debt (already!)
• We need a build framework…
26
What are our next steps?

27
What are our next steps?
Win the SVN + Kerberos battle

• Custom SVN sub system for Jenkins + custom Ant task
• Allows svn+ssh with Kerberos for our setup. _Massive_ speedup
• At some point we will contribute this to the Jenkins community…
28
What are our next steps?
The Build Framework

• Collect learnings and known requirements
• Derive a flexible framework
• Unify maintenance and interfaces to internal customers

Either we automize things further or we need tons of people doing frustrating stuff.
We don’t like frustrating stuff.
29
What are our next steps?
The canonical build pipeline in Jenkins

https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin

• Learn from the ThoughtWorks guys!
• Interesting: build pipeline plugin – Centrum Systems
30
“If something hurts, do it
more often”

31
Contact us
Bigpoint GmbH
Nils Hofmeister
Lead Integration Architect
Drehbahn 47-48
20354 Hamburg
Germany
Tel +49 40.88 14 13 - 0
Fax +49 40.88 14 13 - 11
info@bigpoint.net
www.bigpoint.net

Bigpoint Inc.

Bigpoint Distribuição de
Entretenimento Online Ltda.

500 Howard Street
Suite 300
San Francisco, CA 94105

Av. Brig. Faria Lima
3729 cj. 528
04538-905 São Paulo
Brazil

Bigpoint GmbH

Bigpoint International Services
Limited

Alexanderstraße 5
10178 Berlin
Germany

1 Villa Zimmermann
Ta’Xbiex Terrace
XBX 1035 Ta’Xbiex
Malta

Find us on
32
Bigpoint GmbH
Nils Hofmeister
Lead Integration Architect
Drehbahn 47-48
20354 Hamburg
Germany
Tel +49 40.88 14 13 - 0
Fax +49 40.88 14 13 - 11

info@bigpoint.net
www.bigpoint.net

Find us on
33

More Related Content

PPTX
The Hiscox DevOps journey @ IBM InterConnect, Las Vegas
PPTX
Computing DevOp Summit
PPTX
DevOps @ IBM DeveloperConnect, Twickenham Stadium
PPTX
Moving From Infrastructure Automation To True DevOps
PPT
software technology benchmarking
PPTX
Making software development processes to work for you
PDF
Salesforce DevOps: Where Do You Start?
PPTX
New DevOps for the DBA
The Hiscox DevOps journey @ IBM InterConnect, Las Vegas
Computing DevOp Summit
DevOps @ IBM DeveloperConnect, Twickenham Stadium
Moving From Infrastructure Automation To True DevOps
software technology benchmarking
Making software development processes to work for you
Salesforce DevOps: Where Do You Start?
New DevOps for the DBA

What's hot (19)

PDF
Standardizing Jenkins with CloudBees Jenkins Team
PDF
Gartner Infrastructure and Operations Summit Berlin 2015 - DevOps Journey
PDF
Flintstones or Jetsons? Jump Start Your Virtual Test Lab
KEY
Continuous Deployment
PDF
DevOps and its impact
PDF
Neal Ford Emergent Design And Evolutionary Architecture
PDF
My first deployment pipeline
PDF
Packaging tool options
PPTX
Why to docker
PDF
How adding a further tool can be a good thing
PDF
Introduction to User Experience Design for Engineers
 
PPTX
Continuous delivery for databases
PDF
PuppetConf 2016: Successful Puppet Implementation in Large Organizations – Ja...
ZIP
Continuous Integration, Build Pipelines and Continuous Deployment
PDF
Continuos Integration and Delivery: from Zero to Hero with TeamCity, Docker a...
PDF
PuppetConf 2016: Continuous Delivery and DevOps with Jenkins and Puppet Enter...
PPTX
Overcoming Roadblocks in ABN AMRO's DevOps journey
PPT
Database continuous integration, unit test and functional test
PPTX
LSCC 2014 "Crafting DevOps: Applying Software Craftsmanship to DevOps"
Standardizing Jenkins with CloudBees Jenkins Team
Gartner Infrastructure and Operations Summit Berlin 2015 - DevOps Journey
Flintstones or Jetsons? Jump Start Your Virtual Test Lab
Continuous Deployment
DevOps and its impact
Neal Ford Emergent Design And Evolutionary Architecture
My first deployment pipeline
Packaging tool options
Why to docker
How adding a further tool can be a good thing
Introduction to User Experience Design for Engineers
 
Continuous delivery for databases
PuppetConf 2016: Successful Puppet Implementation in Large Organizations – Ja...
Continuous Integration, Build Pipelines and Continuous Deployment
Continuos Integration and Delivery: from Zero to Hero with TeamCity, Docker a...
PuppetConf 2016: Continuous Delivery and DevOps with Jenkins and Puppet Enter...
Overcoming Roadblocks in ABN AMRO's DevOps journey
Database continuous integration, unit test and functional test
LSCC 2014 "Crafting DevOps: Applying Software Craftsmanship to DevOps"
Ad

Viewers also liked (8)

PDF
Build & deploy PHP application (intro level)
PDF
Continous Delivering a PHP application
PDF
Practical PHP Deployment with Jenkins
PDF
Building and deploying PHP applications with Phing
PDF
Deploy and Scale your PHP App with AWS ElasticBeanstalk and Docker- PHPTour L...
ODP
Continuous Integration and PHP
PDF
Enterprise PHP Development - ZendCon 2008
PDF
Principles and Practices in Continuous Deployment at Etsy
Build & deploy PHP application (intro level)
Continous Delivering a PHP application
Practical PHP Deployment with Jenkins
Building and deploying PHP applications with Phing
Deploy and Scale your PHP App with AWS ElasticBeanstalk and Docker- PHPTour L...
Continuous Integration and PHP
Enterprise PHP Development - ZendCon 2008
Principles and Practices in Continuous Deployment at Etsy
Ad

Similar to PHP Unconference Continuous Integration (20)

PDF
DevOpsCon 2015 - DevOps in Mobile Games
PDF
Ci & proServer
PDF
Architectural Decisions: Smoothly and Consistently
PDF
Architectural Decisions: Smoothly and Consistently
PPTX
Continuous Integration
PPTX
DevOps Days Ohio
PDF
Continuous Delivery: releasing Better and Faster at Dashlane
PPT
FLIGHT Amsterdam Presentation - From Protex to Hub
PDF
Building cloud native microservices
PDF
Confoo-Montreal-2016: Controlling Your Environments using Infrastructure as Code
PDF
August Webinar - Water Cooler Talks: A Look into a Developer's Workbench
PPTX
DockerCon 15 Keynote - Day 2
PPTX
Development Processes and Tooling
PDF
Facilitating continuous delivery in a FinTech world with Salt, Jenkins, Nexus...
PDF
Facilitating continuous delivery in a FinTech world with Salt, Jenkins, Nexus...
PPTX
#spsclt18 vincent biret #spfx #devops
PDF
Continuous Integration with Cloud Foundry Concourse and Docker on OpenPOWER
PPTX
Automation: The Good, The Bad and The Ugly with DevOpsGuys - AppD Summit Europe
PPTX
DevOpsGuys - DevOps Automation - The Good, The Bad and The Ugly
PPTX
Introduction to jenkins for the net developer
DevOpsCon 2015 - DevOps in Mobile Games
Ci & proServer
Architectural Decisions: Smoothly and Consistently
Architectural Decisions: Smoothly and Consistently
Continuous Integration
DevOps Days Ohio
Continuous Delivery: releasing Better and Faster at Dashlane
FLIGHT Amsterdam Presentation - From Protex to Hub
Building cloud native microservices
Confoo-Montreal-2016: Controlling Your Environments using Infrastructure as Code
August Webinar - Water Cooler Talks: A Look into a Developer's Workbench
DockerCon 15 Keynote - Day 2
Development Processes and Tooling
Facilitating continuous delivery in a FinTech world with Salt, Jenkins, Nexus...
Facilitating continuous delivery in a FinTech world with Salt, Jenkins, Nexus...
#spsclt18 vincent biret #spfx #devops
Continuous Integration with Cloud Foundry Concourse and Docker on OpenPOWER
Automation: The Good, The Bad and The Ugly with DevOpsGuys - AppD Summit Europe
DevOpsGuys - DevOps Automation - The Good, The Bad and The Ugly
Introduction to jenkins for the net developer

Recently uploaded (20)

PDF
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
PPTX
VMware vSphere Foundation How to Sell Presentation-Ver1.4-2-14-2024.pptx
PDF
Optimiser vos workloads AI/ML sur Amazon EC2 et AWS Graviton
PDF
Network Security Unit 5.pdf for BCA BBA.
PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
PDF
Per capita expenditure prediction using model stacking based on satellite ima...
PPTX
Understanding_Digital_Forensics_Presentation.pptx
PDF
Electronic commerce courselecture one. Pdf
PDF
Advanced Soft Computing BINUS July 2025.pdf
PPTX
Big Data Technologies - Introduction.pptx
PDF
Advanced methodologies resolving dimensionality complications for autism neur...
PDF
GDG Cloud Iasi [PUBLIC] Florian Blaga - Unveiling the Evolution of Cybersecur...
PDF
Advanced IT Governance
PDF
Mobile App Security Testing_ A Comprehensive Guide.pdf
PDF
[발표본] 너의 과제는 클라우드에 있어_KTDS_김동현_20250524.pdf
PDF
NewMind AI Weekly Chronicles - August'25 Week I
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
PDF
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
PDF
Spectral efficient network and resource selection model in 5G networks
PDF
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
VMware vSphere Foundation How to Sell Presentation-Ver1.4-2-14-2024.pptx
Optimiser vos workloads AI/ML sur Amazon EC2 et AWS Graviton
Network Security Unit 5.pdf for BCA BBA.
Reach Out and Touch Someone: Haptics and Empathic Computing
Per capita expenditure prediction using model stacking based on satellite ima...
Understanding_Digital_Forensics_Presentation.pptx
Electronic commerce courselecture one. Pdf
Advanced Soft Computing BINUS July 2025.pdf
Big Data Technologies - Introduction.pptx
Advanced methodologies resolving dimensionality complications for autism neur...
GDG Cloud Iasi [PUBLIC] Florian Blaga - Unveiling the Evolution of Cybersecur...
Advanced IT Governance
Mobile App Security Testing_ A Comprehensive Guide.pdf
[발표본] 너의 과제는 클라우드에 있어_KTDS_김동현_20250524.pdf
NewMind AI Weekly Chronicles - August'25 Week I
The Rise and Fall of 3GPP – Time for a Sabbatical?
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
Spectral efficient network and resource selection model in 5G networks
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf

PHP Unconference Continuous Integration

  • 1. Continuous Integration for Heterogeneous Environments Nils Hofmeister, 11.09.2011 PHP Unconference
  • 2. Hello world! • Nils Hofmeister • 5+ Years experience in realtime 3D / C++ • 2+ Years experience in web-based games (php, javascript, Java, C++, C#) • Lead Integration Architect @Bigpoint, Hamburg – “the SVN guy” ;) 2
  • 3. Agenda • What is continuous integration? • Why do you want continuous integration for your project? • How do we implement continuous integration at Bigpoint? • What are our next steps? 3
  • 5. What is continuous integration? The gossip • A way to automize certain tasks, e.g. • code validation • build automation • packaging of products • A system of cooperating hardware- and software components , e.g. • Source code management system (SCM) • Staging system + production servers • Build cluster with all kinds of compilers and frameworks on it The idea behind this is much more important, so we do the technical stuff later. 5
  • 6. What is continuous integration? The idea • Not brand-new: First known example: IBM OS/360, early 60s • Current ideas and drivers closely related to agile movement and Extreme Programming • Martin Fowler says: • • • • • • • software development practice integrate *…+ frequently multiple integrations per day verified by an automated build detect integration errors significantly reduced integration problems develop cohesive software more rapidly Martin Fowler on Continuous Integration - 2006 version Original article – 2000 6
  • 7. What is continuous integration? The philosophy Jez Humble says in "Continuous Delivery": • • • • • • • • Create a repeatable, reliable process [...] Automate almost everything Keep everything in version control If it hurts, do it more freqeuntly and bring the pain forward Build quality in Done means released Everybody is responsible for the delivery process Continuous improvement “If something hurts, do it more often” 7
  • 8. What is continuous integration? The attitude • Accept that CI is a standard tool. Just as compilers, SCMs or documentation are • Understand that failing builds must have highest priority - always! • Keep in mind that errors happen anyway. CI only makes them visible immediately and reliably. 8
  • 9. Why do you want continuous integration for your project? 9
  • 10. Why do you want continuous integration for your project? Reduce risks • Defects are detected and fixed sooner • Health of software is measurable • Reduce assumptions (environment variables, local setup, etc) 10
  • 11. Why do you want continuous integration for your project? Reduce repetitive manual processes • Process runs the same way every time • The process starts automatically • This frees resources for higher-value work 11
  • 12. Why do you want continuous integration for your project? Generate deployable software • Product is deployable always • Paradigm-shift from crunch time before release to "always ready to deliver" 12
  • 13. Why do you want continuous integration for your project? Better project visibility • Supports effective decisions • Facilitates recognizing trends 13
  • 14. Why do you want continuous integration for your project? Greater confidence in your project • CI provides a safety net to avoid releasing flawed software • Developers get a better feeling for impact of changes 14
  • 15. How do we implement continuous integration at Bigpoint? 15
  • 16. How do we implement continuous integration at Bigpoint? The setting • Websites, backend systems, clients • PHP is one of many technologies required to assemble our games (an important one, don’t worry ;)) 16
  • 17. How do we implement continuous integration at Bigpoint? The requirements • Per artifact: • Check for defects • Measure quality • Per project: • Assemble deliverable packages • Deploy these 17
  • 18. How do we implement continuous integration at Bigpoint? The solution space (subjective! and there is more of course) Microsoft Team Foundation Server Integrates fine with Microsoft Tools. But with nothing else  TeamCity Well-known product by JetBrains. Feature set is fine, but no USP that justifies to pay for it right now. CruiseControl The classic invented by ThoughtWorks. Now an open source project. Delightfully old-school. Bamboo Quite solid, full-featured product by Atlassian. No real USP though that justifies the high price. Go The current CI solution by ThoughtWorks. The theory behind it is cool but it lacks a lot of features and configuration is no fun. 18
  • 19. How do we implement continuous integration at Bigpoint? The actual solution for us • Hudson: • Created by Kohsuke Kawaguchi • "Duke's Choice Award" in 2008 • Comes from the Java world, ships with CVS/SVN, Maven, JUnit support • Jenkins: • Kohsuke was working for Sun till Oracle acquired Sun in 2010 • Conflict between the Hudson Core developers and Oracle => Fork in 2011 19
  • 20. How do we implement continuous integration at Bigpoint? The actual solution for us II • Trends after fork • Hudson => Focus on quality & stability • Jenkins => Core developers, faster pace • Our decision • choose Jenkins as for us features > stability. • to compensate we use Jenkins LTS 20
  • 21. How do we implement continuous integration at Bigpoint? The actual solution for us III We like the Jenkins community! (My colleague Marcelo and Kohsuke on their way to get their hands on some beer) 21
  • 22. How do we implement continuous integration at Bigpoint? Hamburg Jenkins cluster There are more instances, but this is the biggest one… • Setup • 1 fileserver as master (Debian) • 3 blades (Debian) • 4 windows workstations • Toolchains • • • • • Java Flash/Flex Php (+ JS, html, CSS) Unity/Mono C++ • Highly customized • Home-grown housekeeping + backup • Custom plugins / actively develop Jenkins • All the stuff needed to deal with Kerberos… 22
  • 23. How do we implement continuous integration at Bigpoint? Hamburg Jenkins cluster II Under the hood: • Unity3D • Unity/Mono + Ant • Java • Maven + some Ant • Artifactory/Nexus (memo: synergies…) • Flash • Ant/Maven (Not sure who will win yet) • C++ • gcc/make via Ant/Shell • PHP/web apps • All glory to Sebastian Bergmann – we more or less use his template… • …plus some mods, e.g. minifiers, CDN stuff, 23
  • 24. How do we implement continuous integration at Bigpoint? Bigpoint standard game build pipeline Behold: join plugin, downstream builds, copy artifacts, parameterized builds. We do not do deployment from within Jenkins but have a custom deployment tool. Interface is SVN tags. 24
  • 25. How do we implement continuous integration at Bigpoint? Bigpoint standard build pipeline II • Oh noes, this is too slow… • Optimize hardware • Parallelize wherever possible • Where not possible, decompose and create additional pipelines • But… this is a SPOF! • • • • Backup _everything_ automatically Fully automized CI server setup Find some replication/failover setup (todo) Remember: everything the CI server does must run on your machine as well! • Wait a minute… no more Ninja-deployment? But we need that to be agile… • No you don’t  25
  • 26. How do we implement continuous integration at Bigpoint? The obstacles • The vast amount of knowledge needed • Understanding the Bigpoint platform (the Release Engineering team is “brand new”) • The different requirements, setup and skills of about 25 groups of stakeholders • Linux/IT-driven platform vs. Java toolchain • Acceptance (everyone claims to like Software Engineering, but some people seem to have a different understanding of what that is  ) We can handle much of this very well by now. Our biggest problem remaining: • Technical debt (already!) • We need a build framework… 26
  • 27. What are our next steps? 27
  • 28. What are our next steps? Win the SVN + Kerberos battle • Custom SVN sub system for Jenkins + custom Ant task • Allows svn+ssh with Kerberos for our setup. _Massive_ speedup • At some point we will contribute this to the Jenkins community… 28
  • 29. What are our next steps? The Build Framework • Collect learnings and known requirements • Derive a flexible framework • Unify maintenance and interfaces to internal customers Either we automize things further or we need tons of people doing frustrating stuff. We don’t like frustrating stuff. 29
  • 30. What are our next steps? The canonical build pipeline in Jenkins https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin • Learn from the ThoughtWorks guys! • Interesting: build pipeline plugin – Centrum Systems 30
  • 31. “If something hurts, do it more often” 31
  • 32. Contact us Bigpoint GmbH Nils Hofmeister Lead Integration Architect Drehbahn 47-48 20354 Hamburg Germany Tel +49 40.88 14 13 - 0 Fax +49 40.88 14 13 - 11 info@bigpoint.net www.bigpoint.net Bigpoint Inc. Bigpoint Distribuição de Entretenimento Online Ltda. 500 Howard Street Suite 300 San Francisco, CA 94105 Av. Brig. Faria Lima 3729 cj. 528 04538-905 São Paulo Brazil Bigpoint GmbH Bigpoint International Services Limited Alexanderstraße 5 10178 Berlin Germany 1 Villa Zimmermann Ta’Xbiex Terrace XBX 1035 Ta’Xbiex Malta Find us on 32
  • 33. Bigpoint GmbH Nils Hofmeister Lead Integration Architect Drehbahn 47-48 20354 Hamburg Germany Tel +49 40.88 14 13 - 0 Fax +49 40.88 14 13 - 11 info@bigpoint.net www.bigpoint.net Find us on 33