-
New Feature
-
Resolution: Unresolved
-
Minor
This is a much needed feature as there is no plugin currently which support creating templates and allow a user to use local build and post-build steps.
EZ-templates plugin provide an excellent way to have local parameters but sometimes it is much needed to have local post build steps. For e.g. i want my junittestresults to generate only for one job post build and not for others or have email templates configured differently for a job than others.
- is blocking
-
-
- Closed
-
[JENKINS-38638] Allow build step and post build steps to differ from templates in EZ-templates plugin
I also think it would be very useful to be able to define local post-build actions as not all can be customized with parameters...
drekbour thanks to let us know if it would be possible ?
What is the hardest ? Is it to separate build and post actions ? Because not sure it is required...
I guess it would be already very good to be able to specify that we want override all publisher (or not). The idea would then be to create an exclusion class for publishers section.
On my side, until we have this implemented I was able to "trick" the email post action by converting template in matrix job with the mailing list as axes and by setting the mailing list as variable in post build action... That is not the best option but it allow us to wait a bit the feature will be implemented...
Christophe LACOMBE
added a comment - - edited I also think it would be very useful to be able to define local post-build actions as not all can be customized with parameters...
drekbour thanks to let us know if it would be possible ?
What is the hardest ? Is it to separate build and post actions ? Because not sure it is required...
I guess it would be already very good to be able to specify that we want override all publisher (or not). The idea would then be to create an exclusion class for publishers section.
On my side, until we have this implemented I was able to "trick" the email post action by converting template in matrix job with the mailing list as axes and by setting the mailing list as variable in post build action... That is not the best option but it allow us to wait a bit the feature will be implemented...
Hard because EZ doesn't have much information on the relationship between parent and child. Child can add, remove, replace, disable or reconfigure any item in the publishers or post-build actions. Template can also do all of the same. To the code these are a just list of items, all EZ knows is they are different for an unknown reason. What should it do?
We require a record of the user intention in order to know how to handle existing differences and new changes.
I was just googling for this feature and arrived here. What I don't see in these comments is a reason for not having the whole "Build" section in the "Features exempted from templating" area. This would be a good starting compromise, it should be really easy to add (just like there is already exemptions for job parameters, build triggers, etc.) and would have allowed using this plugin at all when the build steps must differ between jobs.
Charles Machalow
added a comment - I was hoping to use ez-templates to have a base version of my general flow that does setup then the child job would do the 'real work'. I don't think its possible to do that type of thing without this since any changes to the build steps in the child get thrown out at the moment.
Charles Machalow
added a comment - I was hoping to use ez-templates to have a base version of my general flow that does setup then the child job would do the 'real work'. I don't think its possible to do that type of thing without this since any changes to the build steps in the child get thrown out at the moment. 
I suspect this is the most wanted feature but also one of the hardest