Return to the Java 11 end of life date of 30 Sep 2024 for the LTS lines
rather than changing it to match the expected 30 Oct 2024 release date
of the first LTS to require Java 17.
Little benefit to LTS users to extend the end of life message until end of October.
Changing the date will cause the administrative monitor to reappear.
Better to leave it hidden if they have decided to hide it.
Alert Java 11 users of 18 Jun 2024 end of life in weekly
Also updates the Java 11 end of life date for Java 11 users running with
the long term support release.
[JENKINS-64553] call ItemListener after updating job via cli
when a job is updated via REST API or CLI, the
ItemListener.fireOnUpdated is now called to inform about the change.
* [JENKINS-64356] call onCreatedFromScratch after creating item via api or cli
When creating jobs via the rest api or cli the call to
onCreatedFromScratch was missing. This can lead to long startup times
when many jobs are created this way.
* remove unused import
* Clarify state of `{Job,LazyBuildMixIn}#createHistoryWidget()` method.
These methods are no longer needed and should not be called nor overridden.
Instead, history widgets are instantiated via `jenkins.widgets.WidgetFactory` annotated with `@Extension`.
* Javadoc
[JENKINS-71356] handle svg cleanup via a xml document
some attributes and elements where removed via regular expressions.
Additionally `stroke:#000 was replaced with currentColor because there
are some icons that still use that.
This had sideeffects when symbols are used that are not just
black/white, e.g. using svg from jenkins artwork via customizable-header
plugin. There are construct like using class attributes and a style
definition referring to the classes. At other places there where color
definitions with `stroke:#000abc` which were incorrectly modified.
svg cleanup is now implemented with DOM manipulation which is more
robust.
5 icons that still used `stroke:#000` are converted to use
`stroke:currentColor`
* Ensure Classloaders have names for debugging
* update incremental version
* simplify name of UberClassloader and update since TODOs
Co-authored-by: Jesse Glick <jglick@cloudbees.com>
* use released version of remoting
* set the minimum version of remoting
* pick up backward compatable remoting version
* update from remoting incremental version to release version
https://github.com/jenkinsci/remoting/releases/tag/3248.v65ecb_254c298
---------
Co-authored-by: Jesse Glick <jglick@cloudbees.com>
* [JENKINS-73090] Handle CR from `LineTransformationOutputStream`
* Spotless
* Strengthening test to assert that actual linefeed is passed to `eol`
* Also needed to adjust `HyperlinkNote` trick
* Fix non-determinism in nested cause tests
For deeplyNestedCauses, quickly triggering a jobs with no quiet period
runs the possibility that a job is triggered while it is still in the
queue. Triggering and waiting for the jobs to execute synchronously
avoids this and also simplifies the code.
The broadlyNesstedCauses test suffers from the same problem, but is
additionally not structured in the way the original issue describes to
reproduce the issue. Using the quiet period argument to scheduleBuild2,
we can reliably produce a graph where each build is triggered by the
other two jobs. An additional final job outside of the loop cuts off the
1 second quiet period from the last loop's iteration so that the test is
never waiting for the quiet period of any jobs even though half of the
schedule operations specify one.
* Re-work nested cause trimming algorithm
* [JENKINS-65829] Fix WorkspaceCleanupThread to consider suffixed workspaces even if original is inexistent
* [JENKINS-65829] Make sur controller system properties is used across all nodes
* [JENKINS-65829] Adapt test for tmp + rename test for libs
* [JENKINS-72947] Support symbols in TopLevelItemDescriptor#getIconClassName()
When adding a new Item via `newJob` the corresponding Decriptor can now
make use of symbols
* update icon
* add test
[JENKINS-58302] call refresh on the Extension providers again
In the case the ExtensionFinder is itself extensible we refresh it again
to catch extensions that would be discovered by a newly installed
extension.
This seems a little overzerlous, as there is only the variant plugin
that I know of, however calling `Jenkins.get().refreshExtensions() from
any point in the `variant` plugin would seem to be a little bit
dangerous as it would call back into a place where the reactor is
already calling back from.
* [JENKINS-18884] Remove 'People' view
* Add placeholder pages when someone tries to access removed URLs
* Remove obsolete UserInfo class, inapplicable tests
* Restore test with a different core-contributed object
It's not entirely clear what this test signifies, given the
existence of `testTopLevelItemIsLegal`, but whatever.
* Remove probably unnecessary code
---------
Co-authored-by: Daniel Beck <daniel-beck@users.noreply.github.com>
* Remove usages of StringUtils#containsIgnoreCase
Signed-off-by: Bob Du <i@bobdu.cc>
* Remove usages of StringUtils#removeStart StringUtils#removeEnd
Signed-off-by: Bob Du <i@bobdu.cc>
* Remove usages of StringUtils#defaultString
Signed-off-by: Bob Du <i@bobdu.cc>
* Remove usages of StringUtils#defaultIfBlank
Signed-off-by: Bob Du <i@bobdu.cc>
* Remove usages of StringUtils#isAlphanumeric
Signed-off-by: Bob Du <i@bobdu.cc>
* Remove usages of StringUtils.EMPTY
Signed-off-by: Bob Du <i@bobdu.cc>
* Remove usages of StringUtils#split
Signed-off-by: Bob Du <i@bobdu.cc>
* Remove usages of StringUtils#startsWithIgnoreCase
Signed-off-by: Bob Du <i@bobdu.cc>
* Remove usages of StringUtils#countMatches
Signed-off-by: Bob Du <i@bobdu.cc>
* Remove usages of StringUtils#endsWithAny
Signed-off-by: Bob Du <i@bobdu.cc>
* fix spotbugs warning
Signed-off-by: Bob Du <i@bobdu.cc>
* Use Objects.toString
Signed-off-by: Bob Du <i@bobdu.cc>
* revert unrelated change
Signed-off-by: Bob Du <i@bobdu.cc>
---------
Signed-off-by: Bob Du <i@bobdu.cc>
* [JENKINS-69191] icon for agent not accepting tasks
This change adds another icon for the case when an agent is not
accepting tasks, e.g. because the retention strategy avoids this.
The makes it easier to decide whether an agent is in a non healthy
state.
A legend button is added below the computer overview table that shows an
explanation for the icons.
* fix style
Basil Crow