We spent quite a bit of time at work today trying to debug why a job wasn't picked up. The root cause was basically that the label was ['a, b, c', d, e] when it should have been [a, b, c, d, e].
Looking at the Lambda logs, we currently only log the not matching label
|
logger.warn(`Received event contains runner labels '${body.workflow_job.labels}' that are not accepted.`); |
but not any further context. Logging the context would have helped quite us root-cause the issue quite faster.