Hi All,
We had an issue here that I would like to mention. I did not have time to sort out the exact details, so I will just have some vague info and suspicion. Maybe it rings a bell for someone to act on it.
- The first thing we noticed was that our main build was not producing any deliverables anymore, even on green builds.
- Investigation showed that all the post build actions had vanished...
- I checked the actual config.xml file on the disk: it contained the post build actions as expected, no problem
- huh, so jenkins did not read the config correctly?
- restart jenkins.... still no post build actions in the web interface
- I dug out that same config from backups over the past few days
- I noticed it had exploded from 11k to 324k a few days back
- a quick diff showed that the hue-light plugin had dumped a shedload of xml in my config file
- huh, more then 300k of config xml to just turn on a light?!?
- one of my colleagues had been playing around with some hue lights for some weeks but that seemed to work correctly
- and the xml config explosion was only a few days back
- I checked the config history from the backup, the hue plugin section in the config was first a modest 9 lines and then suddenly exploded to a whopping 5000 lines
- a massive "<lightController>" entry was added to the config of the hue plugin.
- as far as we know there was no manual action at the time of the confg.xml explosion
- what else could re-write the config.xml file?
The result was that jenkins got lost in the massive xml (or there was an xml error in there, I did not check all 5000 lines!) and jenkins was missing all of our post actions.
We needed to get the system in good order again quickly, so I restored a config.xml from a recent backup and restarted jenkins. The post actions have returned and life is good again (without the hue light feedback of course :-(....).
Any bells ringing for anyone?
We will probably try the hue plugin once again, carefully...
I will keep this list posted with further experiences.
Cheers,
Tom