Often we'd like to trigger one job with different configuration at many stages of the pipeline.

As far as I can tell the plugin does not support this: the workaround is to create many jobs that are the same(apart from config) and trigger this new job from each stage in the pipeline.

This is undesirable as it increases the burden of keeping the job definitions the same.

The solution IMO would be to add an option to 'inherit' the pipeline stage name from the calling job, or support a list of pipeline stages in the delivery pipeline configuration.