Some of them just have UNKNOWN
Ignoring upgrade jobs at first, it should hopefully be pretty easy to start with master, and copy through the other jobs
All jobs should have owners! :-)
I totally agree, just taking it in chunks for now
... comment button is too close button
sig-release owns all of them?
sig-release owns the dashboard, but we're not responsible for keeping the jobs passing... it's about having a PoC to go bug if the job starts failing... who do I contact first, that can route me to the appropriate person who is or should be fixing the problem, if the entire job is failing, or is failing a test case that other jobs aren't failing?
@BenTheElder
All jobs should have owners! :-)
for release in master 1.8 1.7 1.6; do
dashboard=sig-release-$release-blocking
echo - $dashboard:
for job in $(<testgrid/config/config.yaml yaml2json | jq ".dashboards | .[] | select(.name==\"$dashboard\").dashboard_tab | .[].test_group_name" --arg dashboard $dashboard | tr -d '"'); do
owners=$(<jobs/config.json jq '.[$job].sigOwners | join(", ")' --arg job $job | tr -d '"');
echo " - $job: $owners"
done
done
/close
no more UNKNOWNS in the list above, calling this done