-
Bug
-
Resolution: Fixed
-
Major
-
None
When a Trigger that extends Trigger<Job> is added to a job as it is being created, the start() method is not called.
There is a test called PipelineTriggersJobPropertyTest#triggerPresentDuringStart which shows that start() is called. But in practice...in a non-test environment, it is not called.
I created a simple MockTrigger that shows this.
How to reproduce:
- build and install plugin from https://github.com/scoheb/mock-trigger
- install workflow-job plugin
- create a pipeline job with a MockTrigger
- save the job
You will notice that the start() method is not called.
This behaviour is not consistent with Freestyle jobs.
- blocks
-
JENKINS-42401 crash when enabling or disabling JMS Messaging Plugin trigger on an existing Pipeline job
- Resolved
- is duplicated by
-
JENKINS-45067 PipelineTriggersJobProperty#startTriggers() throws NPE when the property is not assigned to job
- Resolved
- relates to
-
JENKINS-44218 Downstream to Upstream Job Build Trigger doesn't work with Github Organization Jobs
- Open
- links to