On 2016-08-15 09:00, Daniel Spilker wrote:
> Ah, sorry. I was on vacation before your vacation so, I couldn't reply
> earlier.
No problem, I should use ";(" instead of ":(". The effect seems to be
achieved and I'm happy about that :).
In general, I'm glad that the issue with @Symbol occurred. It drove me
to dive into the problem and in the end thanks to caching the overall
performance is much better even than before the regression. It is
especially visible in the seed jobs generating hundreds or thousands of
jobs!
Before fixing that I was planning to get onto the way to make seed job
execution paralleled, but currently the ROI just seems to be too low.
Anyway, I'm still a little bit concerns about live-long caching all
those Jenkins' DescribableModel. Can they be removed in Jenkins (by some
other operations outside job-dsl) or can the reference be changed
leaving job-dsl plugin with outdated elements?
Marcin
http://blog.solidsoft.info/ - Working code is not enough