-
New Feature
-
Resolution: Fixed
-
Major
Currently hudson.plugins.parameterizedtrigger.BuildTriggerConfig and related classes is designed to assume that the downstream project is an AbstractProject, preventing it from triggering a WorkflowJob in schedule (see also perform, perform2, DescriptorImpl.doCheckProjects, etc.).
This could probably be relaxed by just checking for a Job & Queue.Task from which you can schedule a job with a little difficulty (check ParameterizedJob.getQuietPeriod and Job.isBuildable); or perhaps SCMTriggerItem whose scheduleBuild2 is more convenient.
Should work smoothly for TriggerBuilder. For BuildTrigger, can work to the extent that canDeclare is made to be false, so that the triggering is done explicitly rather than via DependencyDeclarer (and thus the DependencyGraph, which at least for now is restricted to AbstractProject).
- depends on
-
JENKINS-30040 Parameterised Trigger Plugin succeeds, then reports failure for workflow jobs.
- Resolved
- is duplicated by
-
JENKINS-27965 Can't trigger workflow job as job from freestyle or multijob project
- Resolved
- is related to
-
JENKINS-29913 Generalize DependencyGraph to Job (or ParameterizedJobMixIn)
- Open
-
JENKINS-26009 Cannot trigger workflow projects using parameterized-trigger-plugin
- Resolved
-
JENKINS-28071 BuildCommand limited to AbstractProject
- Resolved
-
JENKINS-28113 BuildTrigger should accept any ParameterizedJob downstream
- Resolved
- links to