* Fix git not in path for Git plugin global config
Git Client Plugin global configuration allows addition of git implementations using GitTool
The field Path was not able to identify git executable. The fix involves changing prefix with
File.seperator instead of File.pathSeperator. This allows Jenkins to find the git exec at the
already existing path.
* Tests added to validate JENKINS-61711 fix
* Improve hamcrest comparison in FormValidationTest
Co-Authored-By: Mark Waite <mark.earl.waite@gmail.com>
* Import matchers for `not`
Co-authored-by: Mark Waite <mark.earl.waite@gmail.com>
* Hide message re disabling implied dependencies when no dependents exist
* Rename CSS class to be clear about when it's added
Co-authored-by: Daniel Beck <daniel-beck@users.noreply.github.com>
* [JENKINS-61479] Fix a bug in FingerprintCleanupThread and add tests.
* Upgraded Hamcrest to Version 2.2. Incorporated Hamcrest assertion for FingerprintCleanupThread tests.
* Blank line removed
* Changed timestamp_millis->Date; Removed unused imports
* Added hamcrest version as a property
* Changed to assert log output
* [JENKINS-5597] don't follow symlinks
add an option that allows to configure the DirectoryScanner used by
ArtifactArchiver to not follow symbolic links. Option is enabled by
default for backwards compatibility.
* missing readresolve
need to resolve in case it is not defined
* add linebreaks at end of file
* add test for not follow symlinks
* fix indentation
* add tests
update ant to 1.10.7 which supports symlinks on windows and is able to
properly ignore them
* change default in jelly to false
* fix test execution
* indentation and help text
This will allow the use of Resource Root URLs for those files.
Additionally, minor UI improvements:
- Explicitly indicate when no file was uploaded
- Do not show original file name on the UI, nobody cares
* Delete ConfidentialStoreRule
* Also delete MockSecretRule so Secret.fromString works
* Secret.SECRET still referenced by SecretHelper in jenkins-test-harness, used by RekeySecretAdminMonitorTest, also copied in publish-over-*-plugin
* RSAConfidentialKey ought to use the same SecureRandom as the ConfidentialStore; this also lets the mock use a fixed seed
* For now ConfidentialStore.secureRandom can be abstract
* Some core unit tests can be rather verbose; set maven.test.redirectTestOutputToFile
* Looks like we need a ConfidentialStoreRule after all
* Restored another couple of usages
Stefan Spieker