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

[Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel

    Details

    • Similar Issues:

      Description

      Problem statement

      So an instance can itself detect it's not able to update, it would need to know it's not on latest. And endpoint to easily do that from the Evergreen Jenkins plugin, and then surface an Admin Monitor alert, would be good.

      Expected

      The backend should expose a publicly accessible endpoint returning the current updateLevel.
      (Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel).

      (This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.)

      Technical asides

      $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channel
      general
      $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level
      188
      

        Attachments

          Activity

          batmat Baptiste Mathus created issue -
          batmat Baptiste Mathus made changes -
          Field Original Value New Value
          Epic Link JENKINS-55833 [ 197227 ]
          batmat Baptiste Mathus made changes -
          Description h3. Problem statement

          To enable

          h3. Expected

          The backend should expose a publicly accessible endpoint returning the current updateLevel.
          (Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel).

          (This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.)

          h3. Technical asides

          {noformat}
          $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channel
          general
          $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level
          188
          {noformat}
          batmat Baptiste Mathus made changes -
          Summary [Evergreen-backend] Expose a publicly accessible endpoint for the current updateLevel [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
          batmat Baptiste Mathus made changes -
          Assignee Baptiste Mathus [ batmat ] R. Tyler Croy [ rtyler ]
          batmat Baptiste Mathus made changes -
          Description h3. Problem statement

          To enable

          h3. Expected

          The backend should expose a publicly accessible endpoint returning the current updateLevel.
          (Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel).

          (This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.)

          h3. Technical asides

          {noformat}
          $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channel
          general
          $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level
          188
          {noformat}
          h3. Problem statement

          So an instance can itself detect it's not able to update, it would need to know it's not on latest. And endpoint to easily do that from the Evergreen Jenkins plugin, and then surface an Admin Monitor alert, would be good.

          h3. Expected

          The backend should expose a publicly accessible endpoint returning the current updateLevel.
          (Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel).

          (This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.)

          h3. Technical asides

          {noformat}
          $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channel
          general
          $ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level
          188
          {noformat}
          bssmasta Billy Bunns made changes -
          Rank Ranked higher

            People

            • Assignee:
              rtyler R. Tyler Croy
              Reporter:
              batmat Baptiste Mathus
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: