The document discusses Arbetsförmedlingen's transition to using Jenkins Enterprise for continuous integration and delivery. It describes how they moved from many separate Jenkins instances to a consolidated setup with Jenkins Enterprise. They created templates for jobs, builders, and pipelines to promote reuse and standardization. This improved their development processes by enabling easier onboarding, cross-functional teams, and giving teams more control over their pipelines. Moving forward, they plan to use Jenkinsfiles and further improve the Jenkins service offered to development teams.

1. Welcome to Jenkinsmeetup
• Fredrik Andersson, Configuration Manager and leader in Continuous delivery and
DevOps on Arbetsformedlingen. fredrik.x.andersson@arbetsformedlingen.se
• Ulf Hedlund, developer and Configuration Manager

2. Arbetsförmedlingen and its IT:
• Arbetsförmedlingen
– 14000 employees in total
– 280 offices
• IT:
– 650 employees
– 4 offices,
– 25 development teams
• Currently on a ”journey of renewal” to
genuinely improve public confidence
• IT operations and development
– Project initiatives PPS
– Product maintenance (Förvaltning) PM3
– Going toward product lifecycle
management
• 200-250 applications, much inhouse
– Going towards more standard and
sourcing

3. Continuous Delivery Initiative
Tools
• 15 Private Jenkins
• Some got ”lost”
WoW
• Project based development
• WaterScrumFalls at best
• Start with CD: Continuous Integration
Culture
• Focus on develop new features
• One way of working
New Tool
• Jenkins Enterprise
• Pipelines, templates, RBAC, Folders
Tools
• Jenkins Enterprise
• 2 Masters, 25 executors, 2000 daily builds
• CI, Testauto, Deploy
WoW
• Continuous Delivery
• Easier onboarding
• Crossfunctional Teams, incl Product owners
Culture
• Decentralized responsibilities
• Take control over your pipeline
Forward
• Delegate pipeline ownership
• .Net
Starting in 2014 Now

4. Where we used to be – A lot of Jenkins ”islands”
Jenkins
1
Jenkins
2
Jenkins
N
Team A
Team B
Team C
Team D
Team E Team F

5. Our wish – Consolidation
Jenkins
Team A
Team B
Team C
Team D
Team E Team F
We wanted to achieve:
• A unified building process
• An easier way to support many teams
How Jenkins Enterprise helped us:
• Job Templates
• Builder Templates
• Folders
• Role-Based Access Control

6. How our templates began to form…
A standard Jenkins job
Clone from Git
New Artifact Version
Build and Test
Create and Push Tag
config.xml
with
parameters
A generic Job Template
Clone from Git
New Artifact Version
Build and Test
Create and Push Tag
Job 1
Parameters
Job 2
Parameters

7. Refactoring templates - Reusability
A generic Job Template 1
Clone from Git
New Artifact Version
Build and Test
Create and Push Tag
A generic Job Template 2
Clone from Git
New Artifact Version
Build and Test Differently
Create and Push Tag
Builder Template
New Artifact Version
Builder Template
Create and Push Tag

8. Pipelines for integration tests and deployment
Job Template 1
Builder
Template 1
Builder
Template 2
Job 1
Parameters
Docker
SoapUI
Docker
Nexus
Deploy
TestEnv
SoapUI
TestEnv
Etc…

9. Pipelines visualization in Jenkins Enterprise

10. Configuration for a job
• Jobspecific parameters

11. Jenkins – What’s next for us?
• Jenkinsfile – Pipeline as Code
– More flexibility for teams who are self-sufficient
• Enable more operational aspects on the Jenkins service
– Offer the right things for the teams

12. Work for us!
• https://www.arbetsformedlingen.se/Om-oss/Jobba-hos-oss.html
• If you are about to do thesis work or is interested in working with IT at
Arbetsförmedlingen send your letter and CV to jobba-med-it@arbetsformedlingen.se