-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 2.138, email-ext 2.68
-
-
2.69
Since JENKINS-18203, it's possible to refer to files (template, script, etc...) to be used by email-ext-plugin and emailext-template-plugin from files defined through config-file-provider-plugin by using the "managed:" prefix.
The issue is that the "managed:" syntax is working fine only when such configuration is done at the top level of Jenkins.
Whereas the config-file-provider-plugin enables also to configure such files at folder level (cf. cloudbees-folder-plugin), with lowest folder level taking precedence in case of files with same name defined at several levels of the folder tree, this "managed:" syntax does not work in such case like it should.
I'm providing a solution in a GitHub pull-request with unit-tests in a separated commit, so that anyone can figure out the failing scenarii before the fix commit.
[JENKINS-60911] email-ext-plugin not loading files through config-file-provider-plugin when defined at folder level
Assignee | Original: Francisco Fernández [ fcojfernandez ] | New: Guillaume CERNIER [ gcernier_amadeus ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Description |
Original:
Since The issue is that the "{{managed:}}" syntax is working fine only when such configuration is done at the top level of Jenkins. Whereas the {{config-file-provider-plugin}} enables also to configure such files at folder level (cf. {{cloudbees-folder-plugin}}), with lowest folder level taking precedence in case of files with same name defined at several levels of the folder tree, this "{{managed:}}" syntax does not work in such case like it should. I'm providing a solution in a GitHub pull-request with unit-tests in a separated commit, so that anyone can figure out the failing scenarii before the fix commit. |
New:
Since The issue is that the "{{managed:}}" syntax is working fine only when such configuration is done at the top level of Jenkins. Whereas the {{config-file-provider-plugin}} enables also to configure such files at folder level (cf. {{cloudbees-folder-plugin}}), with lowest folder level taking precedence in case of files with same name defined at several levels of the folder tree, this "{{managed:}}" syntax does not work in such case like it should. I'm providing a solution in a [GitHub pull-request|https://github.com/jenkinsci/email-ext-plugin/pull/196] with unit-tests in a separated commit, so that anyone can figure out the failing scenarii before the fix commit. |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Fixed but Unreleased [ 10203 ] |
Comment | [ The [GitHub pull-request|https://github.com/jenkinsci/email-ext-plugin/pull/196] fixing the issue. ] |
Released As | New: 2.69 | |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Closed [ 6 ] |