Job cascading/inheritance issues [message #929557] |
Mon, 01 October 2012 15:05 |
Glyn Normington Messages: 1222 Registered: July 2009 |
Senior Member |
|
|
I'm trying to apply Hudson's job cascading/inheritance feature to Eclipse Virgo which has a large number of CI jobs sharing much configuration data in common. It's hard to make common configuration changes as every job needs to be changed. Also it's tricky to spot where one job has gotten out of step with the others. So job inheritance, or "cascading", seemed to be just the ticket.
However, I've hit two issues which mean that there isn't as much value in the feature as I had hoped. Note that I'm using Hudson 2.2.1.
The first issue is that it is not immediately obvious which configuration parameters are inherited (see footnote 1) and the only way to check is to change them in the child and see if they turn orange. For example, the Post-build Actions section does not appear to be inherited because when I set the child job's files to archive to a different value to the parent, the value doesn't show up as overridden. Another example is that when I set the child's Build Environment timeout value to a value different to the parent, it does not show as overridden.
The second issue is that the granularity of overriding is rather large. For example, I have a job-specific build file in the child's Build section, but setting this turns the whole Build section orange. So if I want to tweak the common (Ant) Targets, also in the build section, I have to do this for each child job even though I never overrode the parent's value.
Also, I've noticed that sometimes the revert button does not appear even when the child configuration is different from the parent and shown in orange. This happens, for example, with the JDK setting.
Footnote 1: According to the feature description "All Job properties will be shown on the Configure Page, by default they will be taken from Parent", but this doesn't seem to be the case. There are tables of job properties which supported cascading in various 2.2.0 betas, so maybe only these properties are overrideable in the shipped version (in my case, 2.2.1). Unfortunately, the table seems incomplete as it doesn't list the Post-build Actions, for example.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02377 seconds