Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-74992

Print relevant pod status changes in build logs

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • kubernetes-plugin
    • None
    • 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).

          [JENKINS-74992] Print relevant pod status changes in build logs

          Antonio Muñiz created issue -
          Vincent Latombe made changes -
          Remote Link New: This issue links to "PR #1627 (Web Link)" [ 30411 ]
          Vincent Latombe made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Vincent Latombe made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Antonio Muñiz made changes -
          Summary Original: Print relevant pod provisioning events in build logs New: Print relevant pod status changes in build logs
          Antonio Muñiz made changes -
          Released As New: 4304.v1b_39d4f98210
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]

            amuniz Antonio Muñiz
            amuniz Antonio Muñiz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: