|
Hi Daniel
That was the whole log, nothing before (except Jenkins starting), nothing after.
There is enough information to improve the code that displays "Failed to parse the build number in the permalink" but doesn't output any useful info to help me fix the issue in the local files. Jenkins is running on a Windows 7 machine, it could be the lastSuccessfulBuild file, sometimes that seems to be a genuine file, and sometimes it is a text file containing a build number. It would be more straightforward if Jenkins never used symbolic links.
PeepholePermalink.java:106
Can this be improved to output the exact path and file that was being searched?
catch (NumberFormatException e) { LOGGER.log(Level.WARNING, "Failed to parse the build number in the permalink cache:" + f, e); // if we fail to read the cache, fall back to the re-computation }
catch (IOException e) { // this happens when the symlink doesn't exist // (and it cannot be distinguished from the case when the actual I/O error happened }
Can the LOGGER be updated to output the path of the file please?
Thank you, Jon
|
