[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title Jonathan Grant commented on JENKINS-32500 Re: Failed to parse the build number in the permalink Hi Daniel Oops, you are right, yes I see it there in this log. I must have confused it with another ticket. Could some recovery mechanism be added? Delete the file, and let the system create a new one after a successful build? It seems a little severe to throw an exception and stop. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title Daniel Beck commented on JENKINS-32500 Re: Failed to parse the build number in the permalink Can this be improved to output the exact path and file that was being searched? Not sure what you mean, the issue says: Failed to parse the build number in the permalink cache:c:\jenkins\jobs\d1h_hello_world\builds\lastSuccessfulBuild Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title
Jonathan Grant commented on JENKINS-32500
Re: Failed to parse the build number in the permalink
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
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title Daniel Beck resolved as Won't Fix Cutting information from the Jenkins log for aesthetic reasons seems like a bad idea. Especially with stack traces, they frequently provide valuable information what's going on. Jenkins / JENKINS-32500 Failed to parse the build number in the permalink Change By: Daniel Beck Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-32500 Failed to parse the build number in the permalink Change By: Oleg Nenashev Component/s: core Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-32500 Failed to parse the build number in the permalink Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title Oleg Nenashev commented on JENKINS-32500 Re: Failed to parse the build number in the permalink Where do you see this issue? The visualization is a minor glitch, which can be fixed easily. But I'm aware there is another root problem causing such empty line Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title Jonathan Grant commented on JENKINS-32500 Re: Failed to parse the build number in the permalink Hello Oleg It is part of the Jenkins server log: http://testmachine:8080/log/all Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
