The issue submitter suggested that the plugin incompatibility message
would be clearer if it specifically referred to the installed version
of the plugin. That seems like an easy change to make and if it helps
a few users, that is great.
Also update the end of life dates for other operating systems based on
https://endoflife.date/ data.
Removes the 'start' entries because we are past the end of life date
of the RHEL 7 derivatives and the one other start date is not needed
because the default start date will cover it correctly.
Confirmed with a CentOS 8 computer that the end of life message
is displayed with the correct date for the CentOS 8 end of life.
The corrected end of life date has already passed, so there may be
Jenkins users that are surprised when their next upgrade reports that
they are running an unsupported operating system.
* experimental flag to run Jenkins without YUI
The YUI library is old and no longer maintained.
Add a user experimental flag to disable YUI. It's disabled by default.
When enabling all the YUI related js libraries and css classes are not
loaded.
Following PR are required to get Jenkins to not show any errors
eventually #7569
Some plugins that use YUI (not complete):
credentials
ldap
global-build-stats
build-monitor
categorized-view
Plugins that make use of makeButton (not complete)
credentials (fixed with https://github.com/jenkinsci/credentials-plugin/pull/533)
openid
acceptance-test-harness
* fix typo
Co-authored-by: Jan Faracik <43062514+janfaracik@users.noreply.github.com>
* add license and restrict class
---------
Co-authored-by: Jan Faracik <43062514+janfaracik@users.noreply.github.com>
* modernise build time trend page
- use jenkins-table
- add time since column
- make the link to the console an explicit icon (like for the agent
history)
- hide the agent column for pipeline jobs
* apply prettier
* missing let declaration
* fix tests
* change flex-direction with media
* apply prettier
* revert change to buildListTable
* [JENKINS-73404] unit test
* roundtrip as Secrets
* [JENKINS-73404] add validation for SecretTextArea
reworked the jelly and simplified the javascript.
the textarea is now always present in the DOM, so no need to remove
inputs to add a textarea. Rather we just remove /hide the "hidden" attribute
from the elements we want to show/hide and give the textArea the
expected class and attributes for validation to occur
* remove unused data-prompt attribute
* Adapt getHiddenSecretValue to backend changes
* Adapt to Secrets being sent as "" rather than null
values for SecretTextArea are now always sent. Whilst this is a change
in behavior the only way once set to unset is to set the value to the
mpty string "" which would still produce a Secret
Additionally this matches the behaviour of f:password and f:textarea
Given both of the above this change in behaviour should not break any
production use cases.
* Remove trailing spaces
---------
Co-authored-by: Mark Waite <mark.earl.waite@gmail.com>
This allows users with `Overall/MANAGE` permission but not `Overall/SYSTEM_READ` to display administrative monitors if the administrative monitor has been implemented to allow it.
* remove idle executors from widget
showing idle executors brings no value. They only blow up the widget.
Instead the busy/total number of executors are added behind the agent
name when the agent is online.
The executor name is kept intentionally to distinguish regular executors
from oneoffexecutors
* feedback
use an icon for oneoffexecutors (FlyweightTask), instead of using a
number for normal executors (which is also not really interesting).
When there are no agents and no builds running use the same text as when
collapsed to show that nothing is running.
* busy in widget header
* fine tuning styling
* icon-xs symbols
* show offline
* show collapsed with no executors
* fix css
* append tooltip to parent
---------
Co-authored-by: Daniel Beck <1831569+daniel-beck@users.noreply.github.com>
* [JENKINS-14789] Configurable interval for computer retention check
Also update the lower bound delay as returned by each RetentionStrategy
from 1min to 0min. This is enabling check intervals of <1min to trigger
a re-check in the next cycle (previously, the nextCheck tracking would
defer the next re-check into the 2nd cycle -- one for the timer loop
and once for the nextCheck timestamp).
Includes a bug fix:
`CloudSlaveRetentionStrategy` tracks the agent timeout in milliseconds
internally and returned the nextCheck delay as a tenth of that.
The nextCheck delay is consumed in minutes, leading to the max delay
of one hour being used.
Fix: Convert the delay from milliseconds to minutes.
Signed-off-by: Jakob Ackermann <das7pad@outlook.com>
* [JENKINS-14789] Allow a check interval of one second
Signed-off-by: Jakob Ackermann <das7pad@outlook.com>
* [JENKINS-14789] Apply review feedback
- Double down on JavaDoc
- Migrate UI to jelly
Co-Authored-By: Alexander Brandes <mc.cache@web.de>
Signed-off-by: Jakob Ackermann <das7pad@outlook.com>
* [JENKINS-14789] Store computerRetentionCheckInterval in model instance
Signed-off-by: Jakob Ackermann <das7pad@outlook.com>
* [JENKINS-14789] Add missing javadoc comment
Signed-off-by: Jakob Ackermann <das7pad@outlook.com>
* [JENKINS-14789] Add tests for model
Signed-off-by: Jakob Ackermann <das7pad@outlook.com>
* [JENKINS-14789] Use AperiodicWork for ComputerRetentionWork
Signed-off-by: Jakob Ackermann <das7pad@outlook.com>
* [JENKINS-14789] limit computer retention check interval to 60s
Signed-off-by: Jakob Ackermann <das7pad@outlook.com>
* [JENKINS-14789] apply review feedback
Co-authored-by: Tim Jacomb <21194782+timja@users.noreply.github.com>
Signed-off-by: Jakob Ackermann <das7pad@outlook.com>
---------
Signed-off-by: Jakob Ackermann <das7pad@outlook.com>
Co-authored-by: Alexander Brandes <mc.cache@web.de>
Co-authored-by: Tim Jacomb <21194782+timja@users.noreply.github.com>
Several of the changes are not detected by the Python script but were
detected by `git grep TODO | grep since` with review of the output.
The cases that are not detected by the Python script seem obscure enough
to not bother with additions to the script. If they become common
practice, then we can extend the Python script.
Markus Winter