Plugin Information
This plugin supports extended configuration for downstream triggers.
It allows to only trigger downstream jobs with SCM changes and gives much more flexibility to configure triggers based on the build result.
Known Issues
- With version 1.2 the behaviour for Matrix jobs changed. Previously a downstream build for each matrix child configuration AND the matrix parent job were triggered. Since 1.2 only the children configurations trigger the downstream builds.
Changelog
Version 1.6
- fixed: (this time for real - well I certainly hope so): upstream build can block if downstream uses a SCM which 'locks' the workspace (e.g. CVS or Perforce) [HUDSON-5406]
- added: you can now configure wich part of a matrix job (parent, configuration, both) should trigger a downstream build [HUDSON-6049]
Version 1.5
- fixed again (hope the fix works this time): upstream build can block if downstream uses a SCM which 'locks' the workspace (e.g. CVS or Perforce) [HUDSON-5406 ]
Version 1.4
- fixed: upstream build can block if downstream uses a SCM which 'locks' the workspace (e.g. CVS or Perforce) [HUDSON-5406 ]
- fixed: workaround for matrix build not being triggered since 1.2 [HUDSON-5508]
Version 1.3
- allow triggering for aborted jobs [HUDSON-5215]
- allow triggering if build result is exactly equal or equal or under the specified threshold [HUDSON-5215]
Version 1.2 (requires Hudson 1.341 or higher)
- show dependency to downstream jobs in build overview page (uses enhancements done to job dependency management introduced in Hudson 1.341)
Version 1.1 (requires Hudson 1.321 or higher)
- allow triggering of downstream job if upstream's build result was failure.
Version 1.0
- initial release. Optionally, restrict triggering to downstream jobs with SCM changes.
Comments (1)
Jan 27, 2010
oeuftete says:
I've opened HUDSON-5406: Downstream-Ext: SCM polling (Perforce) fails for projec...I've opened HUDSON-5406: Downstream-Ext: SCM polling (Perforce) fails for project with a build in progress. There's no downstream-ext component in JIRA, so it might be missed.