-
Bug
-
Resolution: Unresolved
-
Major
-
None
getJobActions is defined for Job/JobProperty but interpreted by AbstractProject.createTransientActions for whatever reason.
Either WorkflowJob should do the same, or a TransientActionFactory<Job<?,?>> should be defined in core which interprets getJobActions (though this would be slightly incompatible as then AbstractProject.getActions would omit them even though AbstractProject.getAllActions would include them).
- is blocking
-
JENKINS-33458 Make Sidebar-Link Plugin Compatible With Pipeline
- Resolved
- is duplicated by
-
JENKINS-25982 JobProperty.getJobActions should be interpreted by Job, not AbstractProject
- Resolved
- is related to
-
JENKINS-30519 Declarative job properties in multibranch
- Resolved