AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
How to Ensure a Trunk Is Always Stable and Ready for Production Release
CI tool, Jenkins, classically is going to pick up your commit or a pull request and run it through a bunch of steps in the pipeline. Some teams use also quite a bit of manual testing for their systems. When you use trunk-based development, is there any space for manual testing? That's a good question and it depends on your intended release cadence.