[JIRA] (JENKINS-41486) the timestamper format is not rememembered across jobs
Title: Message Title Steven G Brown commented on JENKINS-41486 Re: the timestamper format is not rememembered across jobs You don't have to convince me. I've already said that it isn't meant to work that way. The cookie path is set to rootURL, or '/' if rootURL isn't defined. Perhaps something has changed in Jenkins so that the plugin can no longer use this value. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41486) the timestamper format is not rememembered across jobs
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-41486 the timestamper format is not rememembered across jobs Change By: Sorin Sbarnea Attachment: sahara-tempest-rhos-coreci #137_rhos-7.0-patches Console [Jenkins] 2017-02-22 16-33-55.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41486) the timestamper format is not rememembered across jobs
Title: Message Title Sorin Sbarnea commented on JENKINS-41486 Re: the timestamper format is not rememembered across jobs Steven G Brown I was able to identify the bug: the cookie is saved but it is useless because it is saved with the full job-execution path. So the value is remembered for /foo-job/123 which is making it kinda useless. I do have hundreds of different job names with thousands of executions and I was expecting to remember this preference for the entire jenkins instance ( path = / ) not for a specific job. Also the current implementation has another side-effect bug: it does clutter jenkins instance with cookies for each job, and is contributing to another known jenkins bug when the max cookie size limit is reached. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41486) the timestamper format is not rememembered across jobs
Title: Message Title Steven G Brown commented on JENKINS-41486 Re: the timestamper format is not rememembered across jobs The selected format is stored with cookies for each Jenkins site. Is this not working for you? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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] (JENKINS-41486) the timestamper format is not rememembered across jobs
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-41486 the timestamper format is not rememembered across jobs Issue Type: Improvement Assignee: Steven G Brown Components: timestamper-plugin Created: 2017/Jan/26 4:29 PM Priority: Major Reporter: Sorin Sbarnea As a user of Jenkins I do find the timestamper format (duration vs time) to be a global preference option that should be remembered, ideally as a user preference option (so it would be retained even across different machines/browsers). Still, if it would be to hard to implement, even the ability to remember the format per browser (cookie) would be much better than the current behavior. Add Comment
