Status: Open (View Workflow)
When accessing a multi-branch pipeline's snippet generator, the context is the multibranch folder, not an individual pipeline job.
This results in the triggers section for prooperties to have the folder's triggers, which are misleading to pipeline creators.
This should show a branch pipeline's applicable triggers instead.
Use case (i.e. "why not just access the branch project?"):
Access to MBPL snippet generator before having Jenkinsfiles. Sort of a chicken/egg problem.
- relates to
JENKINS-46286 logs contain ClassCastException at PeriodicFolderTrigger
At a minimum, PipelineTriggersJobProperty/config.jelly needs to ignore an it which is not in fact a Job, to avoid offering unusable properties. CC abayer.
Ideally from the folder, we would show triggers applicable to WorkflowJob. Unfortunately this is impossible using current core APIs: TriggerDescriptor.isApplicable takes an Item not a Class<? extends Item>. We could inspect the type parameter of the Trigger (klazz), though this is less precise.
If there is already at least one branch project, we could try to redirect to its pipeline-syntax/ page.
Came up in https://botbot.me/freenode/jenkins/2016-12-08/?msg=77693236&page=8 until https://botbot.me/freenode/jenkins/2016-12-08/?msg=77694239&page=9