The idea behind this gist is to capture the concept of utilizing the Jira Project Automation to create a testable deployment. Here are the general steps:
- Jira: when an issue is transition to a "TESTING" status its triggers a build of the related git repository and branch
- Jenkins: receives a parameter for the Jira ticket ID and retrieves the ticket's dev-status then builds and pushes an image and lastly updates a Helm Chart
- RKE2: Rancher environment monitors git repository containing the Helm Chart to pull new image for application testable deployment
- Email: Testers are notified that testable deployment is available
https://{JENKINS_HOST}/job/{JOB_NAME}/job/{SUB_JOB_NAME}/buildWithParameters?ticket_key={{issue.key}}&ticket_id={{issue.id}}