EnvironmentContributor is the worst thing for trigger plugins imho. Trigger plugins injecting known and safe named variables, they should never be filtered out from job variables. Hiding vars for already setuped envs sounds like a disaster.
On Thursday, May 12, 2016 at 5:54:26 PM UTC+3, Daniel Beck wrote: > > > > On 12.05.2016, at 16:47, Robert Sandell <rsan...@cloudbees.com > <javascript:>> wrote: > > > > But at the same time I need to get a fix out for my users. > > I fear that early implementations to handle this new restriction will be > heavily copy/pasted. So even if you intend to switch to a different > approach as soon as you consider it viable, other plugins may not, > perpetuating this hackish approach. > > -- 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/12838f54-8c52-4bc8-95c2-916c9f011bd3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
