Looks handy but needs some work to use. The 2 types of unique id systems I use day to day are JIRA, and Git(hub).
JIRA uses the monotonically increasing id with project name, github uses a contend addressible hash type of thing. The JIRA numbers are obviously more memorable, but the ability of git to take just a prefix of the hash (as long as it is unique enough) is a nice affordance for human users that may be shouting IDs across a room ;) I wonder if something like this, combined with a human-readable slug, could make for an interesting alternative URI scheme. Like for example, lets take stackoverflow.com, a url like: http://stackoverflow.com/questions/26863972/how-to-prevent-neterr-incomplete-chunked-encoding-when-using-html5-server-even the id: 26863972 is really all that is needed. In fact if you call http://stackoverflow.com/questions/26863972/ - it returns a 301 to the URL with that id and the human readable slug (so its always in your browser). Nice touch for usability, but also gives that unique id that is unchanging. Would this type of alternative scheme interest people in jenkins? then it doesn't matter where a job is buried, the access would be uniform, by id, but with a slug added to aid in comprehention of the url? On Friday, July 15, 2016 at 12:44:30 AM UTC+10, Tom Fennelly wrote: > > On Thursday, July 14, 2016 at 3:16:10 PM UTC+1, Daniel Beck wrote: >> >> https://wiki.jenkins-ci.org/display/JENKINS/Unique+ID+Plugin >> > > Thanks Daniel. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4948dea9-4fba-45ec-8954-c0e04c9bee9d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
