* 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
* [JENKINS-73114] avoid conflict of css classes with bootstrap
jenkins and bootstrap both have definitions for alert and alert-warning,
alert-info, alert-danger. Bootstrap css definitions are included when
e.g. the warning-ng plugin is installed and a job is configured to scan
for warnings. The css classes from bootstrap are then chosen instead of
the ones for Jenkins for things like the admin monitors.
To make things umambiguous, add additional classes prefixed with
`jenkins-` and make use of them in code. Keep the old definitions for
backward compatibility with plugins.
Followup changes are needed in plugins (Mostly those that define admin
monitors) and the design-library
* fix test
* [JENKINS-73158] avoid jumping layout due to tooltips
The fix for JENKINS-72744 made the tooltip get appended to the parent
element. But this can also cause troubles in some cases.
To avoid this one can now decide whether the tooltip should be appended
to the body (the default) or to the parent.
Adjust all locations where a tooltip is displayed inside a widget to
append it to the parent. This works well with those tooltips and avoids
a jumping layout in the custom-folder-icon and potentially other places.
* explicitly append to parent
* fix attribute
* 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
dependabot[bot]
Jan Faracik
renovate[bot]
Jenkins Release Bot
Basil Crow
Zbynek Konecny
Vincent Latombe
Markus Winter
Allan Burdajewicz
James Nord
Jesse Glick
Kevin Guerroudj
Scott K Logan