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

Implement the Evergreen Automated Rollback system

    XMLWordPrintable

Details

    • Epic
    • Resolution: Won't Do
    • Critical
    • evergreen
    • Evergreen Automatic Rollback System
    • Evergreen - Milestone 1, Evergreen - Milestone 2

    Description

      The automated rollback system has been designed, but not implemented yet.

      Related JEPs/documents:

      • JEP 302 for the Git based snapshotting system
      • JEP 306 for the healthchecking

      Acceptance criteria

      1. Set up an evergreen instance, it is at UL-X
      2. publish a (broken) update level (example: adding a plugin without a required dependency) => instance upgrades to UL-X
      3. after restart, evergreen client detects Jenkins cannot restart, and rolls back to UL-X.
      4. Jenkins is accessible again
      5. a correct UL is published, Jenkins can upgrade to it

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. JENKINS-53324 Author a jenkins.io blog post announcing Milestone 1

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          depends on

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-53983 Per-instance tainting still serves the tainted level if you're "coming from" a lower level

          • Blocker - Blocks development and/or testing work, production could not run.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-53964 Drop uuid_checksum_uniq unique key constraint

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. JENKINS-53499 Improve tests to avoid race condition for updates during startup

          • Major - Major loss of function.
          • Closed
          is blocking

          Task - A task that needs to be done. JENKINS-53419 Demo Jenkins Evergreen successfully at DevOps World Jenkins World in SF

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved

          Activity

            People

              batmat Baptiste Mathus
              batmat Baptiste Mathus
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: