-
Bug
-
Resolution: Fixed
-
Major
-
Windows
When trying to add a custom groovy script to a promotion process on windows, an invalid classpath is set preventing the script from running. If you delete the classpath, it returns on the next save of the project.
- is duplicated by
-
JENKINS-49487 Groovy Postbuild under Promotion Actions always opens empty "Classpath entry" resulting "Save" exception
-
- Resolved
-
-
JENKINS-42725 Active Choises Parameter - empty 'Classpath entry'
-
- Resolved
-
- is related to
-
JENKINS-44824 "minimum" of f:repeatableProperty is inherit from ancestors
-
- Resolved
-
- links to
[JENKINS-37599] f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] | New: Jesse Glick [ jglick ] |
Summary | Original: Custom groovy script for promoted builds not working on windows | New: Custom groovy script for promoted builds always including classpath entry |
Component/s | New: core [ 15593 ] | |
Component/s | Original: script-security-plugin [ 18520 ] | |
Assignee | Original: Jesse Glick [ jglick ] | |
Priority | Original: Critical [ 2 ] | New: Major [ 3 ] |
Remote Link | New: This issue links to "script-security PR 84 (Web Link)" [ 14864 ] |
Summary | Original: Custom groovy script for promoted builds always including classpath entry | New: f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry) |
Labels | New: jelly |
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is duplicated by |
Assignee | New: ikedam [ ikedam ] |
Link |
New:
This issue is related to |