On Friday, February 1, 2019 at 12:04:26 AM UTC, Daniel Becroft wrote: > > We had a similar issue, and it ended up being related to MSBuild itself, > not Jenkins. The jobs seemed to work correctly when run from a command > line, but it took a while and they eventually started failing as well. > > Our issue was due to the maximum number of temp files in %TEMP% being > exceeded (see the GetTempFileNameA[1] function, it has an internal limit of > 65,535). Once we cleared those out (and resolved the bug in our code that > wasn't cleaning them up), the builds worked again. > > [1] - > https://docs.microsoft.com/en-us/windows/desktop/api/fileapi/nf-fileapi-gettempfilenamea > > That sounds like a weird one. I had a look at %TEMP% and there were only about 50 or so files at a time there. The build agents are on-demand so they usually only run a handful of builds before being torn down.
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/00594064-0c54-432d-a1d7-7bf938c9989a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
