So which option is this in the GSoC proposal - under "New Job Creation" there are 3 things that were proposed - the first one (new job creation wizard) seems somewhat redundant with Jenkins 2.0 which totally reworked that screen. The second option was job name validation, which is also more "real time" than it was before (although it isn't as you type now, it is only when it loses focus. Given these changes, the third proposal may make more sense:
[Optional] Simple new job configuration. ○ After creation, a new job are configured in the same creation popup. ○ This configuration contain only essential options such as SCM and main build actions. This would be interesting to see - the config page has been redesigned but it still doesn't directly guide you to setting up SCM and other critical things yet. Is that a better place to look? On Thursday, May 19, 2016 at 4:33:13 AM UTC+10, Kirill Merkushev wrote: > > As for configuration functionality on newJob page - what kind of > functionality do you want to see on this page (popup)? Build triggers can > be very complicated in their configuration, so i suggest to not to place it > there > > > 2016-05-18 21:30 GMT+03:00 Kirill Merkushev <twil...@gmail.com > <javascript:>>: > >> - https://wiki.jenkins-ci.org/display/JENKINS/Form+Validation >> - https://wiki.jenkins-ci.org/display/JENKINS/Web+Method >> >> You can save validation logic on the server side (as of any client side >> validation logic may be overridden), but change the trigger for ajax >> request to keypress. >> >> 2016-05-18 17:48 GMT+03:00 Samat Davletshin <sama...@gmail.com >> <javascript:>>: >> >>> I also do not quite get how name validation happens on newJob creation. >>> add-item.js sends GET request to localhost:8080/jenkins/checkJobName >>> If the job name is incorrect it receives an error string "message". >>> >>> Where can see what happens at /checkJobName? >>> Are there any problems with the check happening on client side in >>> JavaScript? >>> >>> It seems to me that job validation should not be very complicated and it >>> would be better to do it on client side. >>> This way it would be possible to give the user a real time feedback and >>> show the warning message right after he typed it. Currently it happens only >>> on blur what is inconvenient in my view. >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Jenkins Developers" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/jenkinsci-dev/fk5deO_SszU/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> jenkinsci-de...@googlegroups.com <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/a2e4bf5a-7a02-441a-8421-feea54b582ad%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/a2e4bf5a-7a02-441a-8421-feea54b582ad%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- 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/bf16a741-9890-45fb-8fc5-899092115d34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
