# Case-Study, Continuous-Deployment, Culture, Practices, Software-Testing, Technical-Leadership, Devel

Published articles for Case-Study, Continuous-Deployment, Culture, Practices, Software-Testing, Technical-Leadership, Devel.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## From two manual monolithic deployments a week to 15+ automated deployments a day

DevFeed: [From two manual monolithic deployments a week to 15+ automated deployments a day](<https://devfeed.tech/articles/from-two-manual-monolithic-deployments-a-week-to-15-automated-deployments-a-day-39883.md>)

Original publisher: [Read original article](<https://mende.io/blog/continuous-deployment-for-the-entire-organisation/>)

Author: tobi@techunicorn.builders (Tobias Mende)

Published: 2022-06-11T13:18:00Z

Content type: article

Language: en

Sources: [Tobias Mende](<https://devfeed.tech/sources/tobias-mende.md>)

Topics: [Deployment](<https://devfeed.tech/topics/deployment.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Git](<https://devfeed.tech/topics/git.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [Back end](<https://devfeed.tech/topics/backend.md>)

Tags: [automated](<https://devfeed.tech/tags/automated.md>), [backend](<https://devfeed.tech/tags/backend.md>), [case-study-continuous-deployment-culture-practices-software-testing-technical-leadership-devel](<https://devfeed.tech/tags/case-study-continuous-deployment-culture-practices-software-testing-technical-leadership-devel.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [deployments](<https://devfeed.tech/tags/deployments.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [e2e](<https://devfeed.tech/tags/e2e.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [git](<https://devfeed.tech/tags/git.md>), [qa](<https://devfeed.tech/tags/qa.md>)

### AI overview

This article describes how BRYTER moved from two manual monolithic deployments per week to more than 15 automated deployments per day. The change enabled continuous production deployments for most applications and services across roughly 15 teams, using a shared Git repository and staging environment.

### Source excerpt

From two manual monolithic deployments a week to 15+ automated deployments a day We did it. Roughly two years after I joined BRYTER and one year after we started the developer experience team, we finally ended the era of manual deployments for roughly 15 teams.