Re: Unreadable data for build wrappers

Thank you! Downgrading 'ruby-runtime' to version 0.12 solved our problem. Den onsdag den 24. august 2016 kl. 14.22.19 UTC+2 skrev Gavin Williams: > Just to update, after some more googling and debugging, I came across: > JENKINS-37422 > > Th

Re: Unreadable data for build wrappers

Just to update, after some more googling and debugging, I came across: JENKINS-37422 The suggestion there is to roll the 'ruby-runtime' plugin back to v0.12. I gave that a go, and like magic all my broken builds have started working again fo

Re: Unreadable data for build wrappers

Not that it helps you Morten, but I've just been hit by the same issue with RVM and Build-Name-Setter. Following a restart, the UI and Jenkins dis-regards any config settings, even though the build config.xml looks correct... I really don't want to have to fettle 20+ jobs every time I have to

Unreadable data for build wrappers

We've been using the RVM and ANSI color plugins for several months now. Suddenly they stopped working after a restart of Jenkins. We generate new jobs from a config.xml template: DISPLAY_NAME false 2 https://server/my_repo.git Nice GUUID