Hi, Instead of creating again a new plugin, the best way to achieve this feature is to extend the EnvInject Jenkins plugin. EnvInject is the centralized plugin to manage environment variables in Jenkins and expose theses variables in the build such as in plugins (for example the artifactdeployer you mentioned).
Additionally, EnvInject plugin provides all elements (frame) to add your environments variables. Feel free to enhance it and provide a Git pull request. Thanks Gregory On Mon, Mar 26, 2012 at 7:10 AM, Baron <[email protected]> wrote: > I would like to make my Maven POM values (e.g. groupId, artifactId, > version, etc.) available as properties for use by other plugins (e.g. > artifact deployer). I started creating a plugin but have hit anumber > of snags: > > - If I create a subclass of BuildWrapper, it looks like I can augment > the environment but it does not appear that the POM has been parsed > yet. > > - I am unclear of whether augmenting the EnvVars is what I want. Does > this make the values available as properties to the rest of the build? > > - I played with registering a MavenReporter where I know I have the > parsed POM but it is not clear how to make these values available to > the rest of the build. > > Thanks for any and all help. > > Baron
