[JIRA] (JENKINS-57201) [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel

[bmathus+ossjira@cloudbees.com (JIRA)]

Baptiste Mathus commented on JENKINS-57201

Re: [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel R. Tyler Croy assigned this to you, after a discussion (yeah, soooo long ago :|). Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[bmathus+ossjira@cloudbees.com (JIRA)]

Baptiste Mathus updated an issue

Jenkins / JENKINS-57201

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

Change By: Baptiste Mathus Summary:

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

Add Comment

[bmathus+ossjira@cloudbees.com (JIRA)]

Baptiste Mathus assigned an issue to R. Tyler Croy

Jenkins / JENKINS-57201 [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel

Change By: Baptiste Mathus Assignee: Baptiste Mathus R. Tyler Croy

Add Comment

[bmathus+ossjira@cloudbees.com (JIRA)]

Baptiste Mathus commented on JENKINS-57201

Re: [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel R. Tyler Croy in case you missed this. When/if you can do it, would be great. Danke!

Add Comment

[bmathus+ossjira@cloudbees.com (JIRA)]

Baptiste Mathus updated an issue

Jenkins / JENKINS-57201

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

Change By: Baptiste Mathus h3. Problem statement To enable 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}

Add Comment