Request to host "Build Env Propagator" plugin

[Vivek Pandey]

As discussed on IRC sometime back about writing a plugin that lets you add new build environment variables or override a pre-defined or existing variables at each build step. 

I have a plugin implemented with these functionalities. 

Basically you can add set of variables at a build step and these will be carried over to the sub-sequent build steps. These variables can also be added/updated any any build step using Jenkins CLI command provided by this plugin. 

My GitHub id is vivek.

Plugin name: "Build Env Propagator"

Github repo name: envpropagator

thanks, 

vivek.

[Daniel Beck]

I'm not a fan of env-inject, but isn't that what its build step basically does when loading env vars from a .properties file?

> --
> 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-de...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Vivek Pandey]

AFAICT, Env-inject plugin injects vars in to a build, it does not get across to other build steps and it doesn't let you modify existing build vars etc.

Vivek

Sent from my iPhone

[Vivek Pandey]

This plugin is currently in my github repo https://github.com/vivek/build-env-propagator.

vivek.

[domi]

As Daniel, i think the env-inject plugin is a pain - but I don't see a clear differentiation to this new one, do we really need an other or would it make sense to combine the two?
Domi

[Vivek Pandey]

I agree there is competing feature of variable injection in a build step, other than that there is not much overlap. Maybe keep them separate to start and merge/add functionalities in to either based on what makes sense after actual usage?

[Daniel Beck]

Just wanted to make you aware of the overlap. Having more plugins lets admins pick and choose, so adding a new one for related but different functionality is preferable from my POV.

[Richard Bywater]

I'm actually of the opposite view in that if we start having lots of plugins with similar functionality, it actually makes things more confusing. Especially if you need to have multiple plugins installed to get the breadth of functionality you want and even more so if they use similar labels on configuration screens.

My 2 cents :)
Richard.

[do...@fortysix.ch]

+100 on Richards comment

We have already by far to many plugins doing “nearly the same”, its impossible for an admin to make a well funded decision. and then there is also to most important point maintenance: the more plugins we have the harder it gets to find a new maintainer or keep the plugin evolving…

A couple of times we had new plugins started with the idea of doing a release now and wanting to merge the feature with a different plugin in the future, but in fact its not going to happen.

Domi