Title: Message Title
Richard Bywater commented on JENKINS-44786
Re: HTML Publisher does not allow environment variables in fields
Matthew Pistella Hector Santana I've hit a bit of a snag which is slowing things down a bit when it comes to using parameters for the report name specifically related to the main job page view. Currently, for the per-build page, I have a solution which is to add a new "Display Name" field where you can use parameters and this is displayed on the left-nav of the per-build page. However, for reasons that appear to be either Jenkins architectural ways of working or my lack of understanding them, this doesn't work very well for the main job page as a) you have to fetch the latest build to get the correct Display Name to show and then b) this appears to be cached and therefore next run the code isn't called to refresh the name of the left nav item on the job page. So, my question to you both is (Matthew, I'm not sure if report name parameters is something you are interested in or if it's one of the other fields): would there still be value, from what you know, of having the ability to have Display Name (which allows parameters) for the per-build left nav view, if the job page view was always only just displaying the value provided in Report Name (the non-parameterised one). If there is no real value, then unfortunately the report name will not be able to have any parameters applied at this stage. I hope I make sense! Let me know your thoughts so that I can make an informed decision about which way to head
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message
