Jenkins 2.7.1 LTS Support

[nickgrealy]

Since Jenkins v2 has been released, the plugin no longer injects the pmt_* variables (as build parameters).

The plugin needs to be updated (and tested) to (only?) support the latest LTS (currently 2.7.1).

[nickgrealy]

Duplicate of https://github.com/jenkinsci/poll-mailbox-trigger-plugin/issues/19

[nickgrealy]

Current workarounds

Do one of the following:

• explicitly add parameters to their jobs (they will be updated by the plugin)
• define a -Dhudson.model.ParametersAction.safeParameters=pmt_from,pmt_replyTo,etc property whitelist
• define a -Dhudson.model.ParametersAction.keepUndefinedParameters=true property

See also

• https://groups.google.com/forum/#!topic/jenkinsci-dev/-gl9_lE546Q
• https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11
• https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170

[nickgrealy]

Missing env vars fixed in commit https://github.com/jenkinsci/poll-mailbox-trigger-plugin/commit/d0154dab63dc3a5978ebcbcd6aaa6d98212009cf

Ready for release

[vijaychandra24]

Since Jenkins v2 has been released, the plugin no longer injects the pmt_* variables (as build parameters So if pmt variables not supported how can we overcome previous requirement trigger based on email from ??

[nickgrealy]

Hi @vijaychandra24,

Thanks for raising this issue.

Can you please re-test using the latest plugin version (1.026) - and if you are still encountering issues, please raise a new issue, providing as much information as possible.

I know for certain that the plugins supports Jenkins LTS 2.7.1 (I just tested now), so perhaps if you are not using version 2.7.1, you could consider moving to this Jenkins version.

Kind regards,

Nick Grealy