• Type: Task
    • Status: Resolved
    • Priority: High
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Marathon 1.5.0
    • Component/s: None
    • Labels:


      The CI seems a little over engineered. This is a prioritized feature list:

      Foreach Phabricator diff and commit to master and releases/* the CI should

      1. [x] Compile the code
      2. [x] Post status to Phabricator and Github
      3. [x] Run scapegoat
      4. [x] Run the unit tests
      5. [x] Archive the test results
      6. [x] Run the integration tests
      7. [x] Archive the integration tests results
      8. [x] Generate tarball package
      9. [x] Generate Docker image
      10. [x] Generate rpm and deb packages
      11. [x] Upload the tarball package to S3. This enables snapshot builds.
      12. [x] Publish test results to Phabricator
      13. [ ] Generate unit test coverage
      14. [ ] Archive unit test coverage
      15. [ ] Generate Scala documentation
      16. [ ] Publish Scala documentation
      17. MARATHON-7361 Create DC/OS snapshots, e.g. through pull requests. MVP might be to publish the tarball location.
      18. [ ] Trigger system integration tests against DC/OS snapshots
      19. MARATHON-7362 Publish rpm and deb packages.

      The implementation should be time boxed to one week. Please note that the CI does not release RCs etc only snapshots for DC/OS open integrations. DC/OS EE releases are not addressed here yet.

      The goal is that the builds for Phabricator diffs and for branches do not differ. Ideally most steps are runnable on a Mac or linux system. Every step must be documented.


          Issue Links



              • Assignee:
                kjeschkies Karsten Jeschkies
                kjeschkies Karsten Jeschkies
                Orchestration Team
                Karsten Jeschkies, Ken Sipe
              • Watchers:
                2 Start watching this issue


                • Created: