Can we make sure that the jenkins artifactory will be used to download these js packages and store them forever (otherwise I am -0.5). without that we could be up the proverbial creek when someones hosting decides to depart / change url etc. etc... (seen it way to often with maven).
so long as I can mvn install without installing extra tools and remembering to set all the specific environment variables then I have no other objections - but to be fair I'm not exactly sure of all the ins and outs of the JS packaging here anyway On Saturday, September 5, 2015 at 1:28:35 PM UTC+1, Tom Fennelly wrote: > > There are a few changes being proposed/planned for Jenkins Core that will > require some UI changes e.g.: > > 1. Unbundling plugins. See dev list thread > <https://groups.google.com/forum/?hl=en#!topic/jenkinsci-dev/kRobm-cxFw8>. > The UI changes here would be a new "Plugin Selection Wizard" to help new > users of Jenkins get up and running quickly, filling the gap left after > removing the currently bundled plugins. > 2. Hopefully making improvement to the config pages ala what KK and > Gus Reiber are doing on the config-ui-changes branch > <https://github.com/jenkinsci/jenkins/tree/config-ui-changes>. > > In order to implement these changes as hoped, we're going to need to use > client-side JavaScript (better UX etc). At the moment, in Jenkins, > JavaScript is a bit of a mess. It would be nice to start addressing this > problem in some way under the assumption that, going forward, we can make > more use of client-side JS for better UX, but do it in a more maintainable > way (Vs everything being in hudson-behavior.js). > > Some of us at CloudBees have been developing and using some patterns and > tools to help build Jenkins plugins that have GUI elements that make better > use of modularized JavaScript (using CommonJS modules etc). We think it has > worked quite well and would be keen to reuse some of the same techniques > and tools in Jenkins core if possible. > > One of the tools we developed to help us assemble these JavaScript > components is a build time utility we call jenkins-js-builder > <https://github.com/tfennelly/jenkins-js-builder>. It's an NPM utility > for assembling CommonJS module "bundles", built on Gulp > <http://gulpjs.com/>, Browserify <http://browserify.org/> and more. > > My question .... would there be community objection to introducing > something like this into Jenkins core? We're not trying to suggest it as a > silver bullet for all JS related issues, but we do think it would help > improve things. > > Regards, > > T. > -- 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/dc82fe44-04d7-4e43-9343-b184a0771c9d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
