Add pod/container name to build logger fields

What does this MR do?

Adds PodName field to Build struct and includes it in log messages after the script stage. This helps identify the specific container or pod executing a job, appearing in messages like 'Job succeeded' alongside hostname and other metadata.

Implemented across executors:

  • Docker: uses container name
  • Kubernetes: uses pod name
  • Docker Machine: tracks in machine details
  • Custom: supports pod_name in config output

Why was this MR needed?

This brings the executor's hostname as well as pod name up into the runner logs.

While some of this information is exposed in the executor logs, it requires either joining across several log lines or consulting the job trace. By having this information in runner logs directly, it becomes much easier to know which VM/pod a job ran on, which is useful for debugging, and potentially also for cost analysis, since we can more easily correlate runner logs with other sources.

What's the best way to test this MR?

I tested it locally.

What are the relevant issue numbers?

n/a

Merge request reports

Loading