Jenkins will run test suites after merges. Once a pull request has progressed through dev & testing, and you have approvals, you can deploy whenever. Occasion

Jenkins will run test suites after merges. Once a pull request has progressed through dev & testing, and you have approvals, you can deploy whenever. Occasionally there are PR's/tickets that relate to each other but most of the time the work is broken up into testable, small chunks of functionality that can be deployed any time they are ready. Sometimes you have to build extra things to follow this process if your changes are shipping ahead of other related changes. Like a feature flag to turn things on/off. In previous jobs this would be seen as waste but with CI/CD it is necessary to allow a continuous flow in the process, which is awesome.