1. Reporting/Visibility - We want this to be repeatable and measurable. * How many total jobs were executed in the last 3 months? How many unique jobs? * How many were identified as "deploy" jobs? (I'm not sure if all the jobs are considered deploy jobs) Looks like this answer is `89 total deploy` from your stats. * How were they identified as "deploy" jobs? Did they contain certain strings we were looking for? * How many unique "deploy" jobs? `71` from your stats. * How many unique "deploy" jobs on prod? `19` from your stats, based on `ECS_CLUSTER=prod` criteria. 2. Scripts * Do we have stats on the scripts to align with above? * `aws_ecs.sh` was used in how many total/unique jobs? Of that, it was used in how many prod deploy jobs? `71` is listed, but I'm not sure is that out of the `89 total deploy` jobs? 3. OpsLevel * We want to: * Create service in OpsLevel if it does not exist. * Update a check (to be created) that is for "Not on Bitbucket" and fail them. * We can add tags to the service in OpsLevel to store the metadata you suggested, such as `jenkins_script` * We will send OpsLevel a deployment descriptor on deployment, including task definition updates.