Execute Groovy scripts and injecting environment variables after SCM

[wenhao]

Currently, this plugin doesn't support Execute Groovy scripts after the SCM step in Build Wrapper.

added few lines to fix it.

[cloudbees-pull-request-builder]

plugins » envinject-plugin #42 UNSTABLE
Looks like there's a problem with this pull request

[wenhao]

Negative, #39 failed on Oct 13, 2013 with same error.

Also I run it on my local all good. I believe somebody need to look into it.

Thank you & Best Regards

Wen Hao(文浩)
Mail: wenhao@126.com
Skype: cdwenhao

On Nov 27, 2013, at 10:33 PM, CloudBees pull request builder plugin notifications@github.com wrote:

plugins » envinject-plugin #42 UNSTABLE
Looks like there's a problem with this pull request

—
Reply to this email directly or view it on GitHub.

[wenhao]

Negative, #39 failed on Oct 13, 2013 with same error.

Also I run it on my local all good. I believe somebody need to look into it.

Thank you & Best Regards

Wen Hao(文浩)
Mail: wenhao@126.com
Skype: cdwenhao

On Nov 27, 2013, at 10:33 PM, CloudBees pull request builder plugin notifications@github.com wrote:

—

[oleg-nenashev]

It makes sense to create an extension point (e.g. EnvInjectProducer) in order to add such features on-demand. Such extensive way is not good...

[jenkinsadmin]

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests