Our CI/CD and release management process at Flagsmith

Flagsmith is committed to transparency and efficiency in its engineering processes, developing its product openly to help teams make informed, long-term decisions about feature flags. The company emphasizes its CI/CD pipeline, which involves several stages to ensure the integrity and performance of their software. This process begins with code creation and review on local machines, primarily using JetBrains or Emacs IDEs, and involves submitting pull requests to their GitHub repository for team review. Automated testing and linting through GitHub Actions ensure code quality before merging it into the main branch. The software is then built and deployed to a staging environment for further testing, simulating production conditions. Once these tests are successful, the code is deployed to production, involving Docker images and AWS ECS deployment, followed by end-to-end testing in a live environment. Finally, Flagsmith differentiates between deployment and release, utilizing feature flags to control the availability of new features and gather user feedback before a full release. This structured approach highlights their dedication to speed, security, and continuous improvement in software development.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.