Further to the below, after realising the number of combinations of
jobs and slaves they run on could I actually ask someone to check on
the Ubuntu slave nodes and clear out any remaining workspace files
that are still present for the Qpid jobs (
https://builds.apache.org/view/M-R/view/Qpid ) ?
I
I can indeed configure them once again. Thanks :)
Robbie
On 27 June 2012 21:13, Olivier Lamy wrote:
> Check again now, I have updated the promoted build plugin.
> All looks better now.
>
>
>
> 2012/6/27 Robbie Gemmell :
>> All of the Qpid jobs are exhibiting this problem. A lot of them are
>> al
Check again now, I have updated the promoted build plugin.
All looks better now.
2012/6/27 Robbie Gemmell :
> All of the Qpid jobs are exhibiting this problem. A lot of them are
> also throwing checksum exceptions during their SVN updates which I was
> hoping to fix by setting the jobs to do a f
All of the Qpid jobs are exhibiting this problem. A lot of them are
also throwing checksum exceptions during their SVN updates which I was
hoping to fix by setting the jobs to do a fresh checkout and running
them on the various nodes they use, but I can't currently configure
them due to this proble
Hi,
Which job are you editing ?
Maybe it's only one plugin which need some upgrade (but not sure about
whole jenkins instance)
Cheers,
--
Olivier
2012/6/27 giridharan kesavan :
> All,
>
> It looks like the recent upgrades of jenkis is broken.
> clicking on job configuration of any job show up the
All,
It looks like the recent upgrades of jenkis is broken.
clicking on job configuration of any job show up the following trace
Status Code: 500
Exception: org.apache.commons.jelly.JellyTagException:
file:/home/hudson/hudson/plugins/promoted-builds/WEB-INF/classes/hudson/plugins/promoted_bu
