Uploaded image for project: 'Marathon'
  1. Marathon
  2. MARATHON-8313

Metronome 0.4 and Marathon 1.6 release branches are waiting for authorization to build on Jenkins

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: DC/OS 1.11.4, RI-3
    • Component/s: None
    • Labels:
      None
    • Sprint:
      Marathon 2018-24
    • Story Points:
      1

      Description

      Our new release branches wait for explicit authorization in order to build. The causes because these branches are new, and inherited the security changes from master, whereas the previous release branches did not include the plug-in. We should modify the Jenkins file on those branches to indicate to the security plug-in that those branches are safe to build.

      This issue affects both Marathon and Metronome

      Here is a recent stalled out build as a result of this issue:

      https://jenkins.mesosphere.com/service/jenkins/job/Metronome/job/metronome-pipelines/job/releases%252F0.4/2/console

      Acceptance Criteria

      Marathon releases/1.6 and Metronome releases/0.4 jobs build automatically for release branches after commits are merged, and do not wait for explicit authorization.

        Attachments

          Activity

            People

            • Assignee:
              tharper Tim Harper
              Reporter:
              tharper Tim Harper
              Team:
              Orchestration Team
              Watchers:
              Tim Harper
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: