Hi, I'm trying to write a plugin that imposes a limit on a build. A previous plugin achieved this using a build wrapper which started a repeating scheduled task. In a pipeline it seems like a build wrapper has to be applied as a block in the script instead of being able to apply to the entire build. This makes it opt-in whereas I'd like to define this limit outside of the script as an administrator.
Is a build wrapper the wrong approach for this behavior? I'd like a parameter on the build config page and a scheduled task which begins when the build starts. Is this style of plugin incompatible with pipelines, or is there a particular approach I should take? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1116fc9c-2636-4e1f-bfc8-07c8fd52e5b5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
