DevOps and Agility Immersed in the Production Factory
summary
BlueMind describes an industrialized delivery pipeline where source code is stored in Git, CI is handled with Jenkins and Docker, and each release runs unit, integration, black‑box and manual acceptance tests before shipping. The stack supports 500+ clients and up to 250,000 users per deployment across eight Linux distributions, multiple browsers and native Outlook compatibility; feature flow uses a suggestion box, product owner, Kanban, peer code review and automated builds, with minor releases twice monthly, same‑day security fixes and 3–4 years of maintenance per major version.
AI-written summary · about
chapters (23)
- 0:00Start
- 1:29Presentation of BlueMind
- 1:50BlueMind users
- 4:03When is a new version released?
- 4:25Multiple developments in parallel
- 5:38The different development branches
- 6:37What does BlueMind represent?
- 7:13Smartphones
- 8:02The Mappy protocol
- 9:06The Linux distribution
- 9:53Languages
- 10:15Documentation
- 11:11The API
- 11:54The BlueMind environment
- 12:28The editor
- 13:52Headquarters
- 16:19The producer
- 17:20The developers
- 18:22Interaction with developers
- 19:39Build process
- 20:43Test coverage
- 21:25Development tools
- 24:20Questions / Answers
related talks
01h 01mA team's transition to Continuous Delivery
46mThe Software Factory
34mEnabling a Continuous Deployment Mindset
41mContinuous Delivery Transformation: The New Way of Working
43mThe Road to DevOps
05mIBM Codename: BlueMix DevOps Services for Rapid Software Delivery
34mDeploy, Release, CI/CD, Oh My! DevOps for the Rest of Us
28mEmbracing On-Prem delivery with DevOps