Le 28/02/2014 23:10, Antoine Musso a écrit :
python-jenkins then verify the job got created using the GET request above. I found out tonight that our misc Varnish caches the 404 error for up to a minute, and hence the second GET is being served the cached 404 by Varnish. End result JJB consider the job hasn't been created and bails out with the above stack trace.
Hello,
This is now fixed. I made the Apache proxy in front of Jenkins to send Cache-Control: no-cache,must-revalidate headers following a suggestion by Mark Bergsma.
Related change is https://gerrit.wikimedia.org/r/116748
I confirmed jobs can now be created properly by JJB.
Thanks Matthew to have raised the issue!