-
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
-
[JENKINS-29880] Honor getJobActions
Link |
New:
This issue is duplicated by |
Link |
New:
This issue is related to |
Link |
New:
This issue is blocking |
Workflow | Original: JNJira [ 164958 ] | New: JNJira + In-Review [ 181760 ] |
Component/s | New: pipeline-general [ 21692 ] |
Component/s | Original: workflow-plugin [ 18820 ] |
Component/s | New: workflow-job-plugin [ 21716 ] | |
Component/s | Original: pipeline [ 21692 ] |