Synchronizing deployments with sprint completion

In Agile scrum, one of the artifacts created during a sprint is the Product increment, which is the deliverable produced by completion of the product backlog tasks during a sprint. In this section, we'll learn how to integrate with Jenkins using automation rules to automatically initiate the final deployment build when the sprint in Jira is closed.

During a sprint, in a trunk-based development model, developers will commit code to the branch in the source repository associated with the development task, which will generally initiate automated tests to verify that the new code does not negatively affect the build process. When pull requests are created and merged, further automated tests can be initiated followed by automated deployments to QA or staging servers. By the time the sprint is completed, all these processes result in the final task of deploying the resultant product increment to production, or by using a tool such...