[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Peter Lieverdink commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing Ken Rachynski Yep, confirmed. I checked the users.xml file and also found an "unknown" entry in there pointing at an old format token in users/foo/config.xml. I've deleted said user, in theory that'll mean the warning doesn't come back after a restart. I am pretty sure that entry in list of users is courtesy of GitHub integration; Jenkins tries to enumerate people its finds in git commits, whether they have actual Jenkins logins or not. The "unknown" user in question has an email address that does match a former staff member, but it's not one that we ever used in LDAP. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193341.1535412226000.9172.1574981220631%40Atlassian.JIRA.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Peter Lieverdink commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing Indeed I can, here is the full list: plugins.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Peter Lieverdink updated an issue Jenkins / JENKINS-53266 Legacy token for user "unknown" keeps reappearing Change By: Peter Lieverdink Attachment: plugins.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Peter Lieverdink created an issue Jenkins / JENKINS-53266 Legacy token for user "unknown" keeps reappearing Issue Type: Bug Assignee: Unassigned Attachments: legacy-setting.png, legacy-warn.png, unknown-user.png Components: core Created: 2018-08-27 23:23 Environment: Jenkins versions 2.130 through 2.140 alpine docker image. Priority: Minor Reporter: Peter Lieverdink Ever since the API token change introduced by JENKINS-32776, a legacy token is automagically generated on our install for the nonexistent user "unknown". Legacy tokens have been disabled since updating to 2.130. After manually revoking the token, it usually takes a few hours for it to magically reappear and then causes the red administrative monitor counter to (re-)appear in the toolbar. Though I can revoke the token, I am unable to change it via the user admin page Change API Token button.
[JIRA] (JENKINS-30319) SSH - Ed25519 keys not supported
Title: Message Title Peter Lieverdink commented on JENKINS-30319 Re: SSH - Ed25519 keys not supported The same goes for other key algorithms. Or rather, not supporting them is one thing, but showing two pages of stack trace when a user enters one is another thing altogether. Basic input validation would allow a user to see they entered an unsupported key type without being presented with a stack trace. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] [blueocean-plugin] (JENKINS-35223) Allow configurable date/time format for all temporal fields in output
Title: Message Title Peter Lieverdink commented on JENKINS-35223 Re: Allow configurable date/time format for all temporal fields in output Works for me! 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] [blueocean-plugin] (JENKINS-35223) Allow configurable date/time format for all temporal fields in output
Title: Message Title Peter Lieverdink commented on JENKINS-35223 Re: Allow configurable date/time format for all temporal fields in output James Dumay Ideally the columns as-is would show the full timestamp, not just on hover. that would make it easier to find a job that ran (or failed) at a specific time without needing to hover on a bunch of them. Michael Neale With explicit timezone would be good, assuming I can specify at run-time via $TZ or via a setting. The work-around I use currently (CompactColumns) doesn't, but does grab the date format from the browser locale. To me that makes it unclear whether the date/time is also taken from the browser or not. An explicit TZ offset would remove that. Alternatively, a configurable format string (I know James Dumay hates settings, I'll buy him a coffee to pacify him next time I see him would allow for more flexibility too. 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] [blueocean-plugin] (JENKINS-35223) Allow configurable date/time format for all temporal fields in output
Title: Message Title Peter Lieverdink created an issue Jenkins / JENKINS-35223 Allow configurable date/time format for all temporal fields in output Issue Type: New Feature Assignee: Michael Neale Components: blueocean-plugin Created: 2016/May/31 4:01 AM Priority: Minor Reporter: Peter Lieverdink Our organisation uses many developers, ops people and servers all located in many different timezones. Though servers are generally (but not always (don't ask)) configured on UTC, apps generally don't use UTC and bug reports filed by users are invariably in the local TZ. To help us reconcile system and application logs and user reports against Jenkins tasks, it would be really helpful if Jenkins had the option to display its temporal information in ISO8601 format, rather than just the "X ago" format. Add Comment
