Print relevant pod status changes in build logs

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 4304.v1b_39d4f98210

      When a pod cannot be scheduled for whatever reason there is no feedback in build logs. This is inconvenient for users when the cause of the pod not being scheduled is a user error (ie. wrong pod template definition).

      All relevant pod events should be printed in build logs (both container status and pod status can contain relevant information for users).

            Assignee:
            Antonio Muñiz
            Reporter:
            Antonio Muñiz
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: