-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display appropriate GUI that accurately displays offline by design #9883
Display appropriate GUI that accurately displays offline by design #9883
Conversation
Reworked computer icon and associated descriptions to be controlled by the `OfflineCause` implementation. For implementations such as `RetentionStrategy.Demand`, this allows to set an offline cause that can't be interpreted by the end user as an error. Introduced `pause` and `computer-paused` symbols, used by the on-demand retention strategy to indicate the computer is offline on purpose and is not in error state Add `getOfflineCause` to `IComputer` and refactor related methods to pull up methods that make sense at the interface level. Extract `IOfflineCause` interface from `OfflineCause`.
Could you add the new icon to https://github.com/jenkinsci/jenkins/blob/master/core/src/main/resources/hudson/model/ComputerSet/_legend.jelly |
I have never even seen that "legend" popup. TIL |
Actually not needed. The existing on-demand retention strategy was putting the agent offline, whereas the current scheduled retention strategy just marks it as suspended (so it actually is connected but can't be used). |
@@ -212,5 +222,28 @@ public static class IdleOfflineCause extends SimpleOfflineCause { | |||
public IdleOfflineCause() { | |||
super(hudson.slaves.Messages._RetentionStrategy_Demand_OfflineIdle()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this wasn't shown before and now is I'd suggest changing the text from computer
to agent
Offline because computer was idle
doesn't make sense as a computer isn't user facing terminology, (not mentioned in https://www.jenkins.io/doc/book/glossary/), it should be agent instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was already shown before, just not before the agent was online, then became offline again as instructed by the retention strategy.
can you add a changelog entry please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/label ready-for-merge
This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.
Thanks!
Reworked computer icon and associated descriptions to be controlled by the
OfflineCause
implementation. For implementations such asRetentionStrategy.Demand
, this allows to set an offline cause that can't be interpreted by the end user as an error.pause
andcomputer-paused
symbols, used by the on-demand retention strategy to indicate the computer is offline on purpose and is not in error stategetOfflineCause
toIComputer
and refactor related methods to pull up methods that make sense at the interface level.IOfflineCause
interface fromOfflineCause
to make it possible to render offline causes in other runtimes (CloudBees CI HA)Screenshots
See JENKINS-XXXXX.
Testing done
Proposed changelog entries
Proposed upgrade guidelines
N/A
Submitter checklist
Desired reviewers
@mention
Before the changes are marked as
ready-for-merge
:Maintainer checklist