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

Better logging

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • marathon-plugin
    • None

      We should (optionally?) log the fields that are being used to replace the Marathon JSON fields to help debugging when things go wrong. Specifically if people use the wrong environment variables (e.g. this DC/OS users list thread).

          [JENKINS-37287] Better logging

          Michael Griffin added a comment -

          The marathon-rendered-$BUILD_NUMBER.json file should contain the entirely to the application definition. Currently, the id, image, and dockerForcePull options are not recorded.

          If i archive the marathon-rendered-$BUILD_NUMBER.json file as an artifact, I should be able to use the file directly to recreate a marathon deployment.

          Michael Griffin added a comment - The marathon-rendered-$BUILD_NUMBER.json file should contain the entirely to the application definition. Currently, the id , image , and dockerForcePull options are not recorded. If i archive the marathon-rendered-$BUILD_NUMBER.json file as an artifact, I should be able to use the file directly to recreate a marathon deployment.

            colinmsphere Colin
            ssk2 Sunil Shah
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: