It seems inevitable to me that improving the Jenkins UI will involve changing how things are done today and that's going to involve introducing something else into the mix. There's no doubt that introducing something else into the mix can make life more difficult in some situation. I suppose the question is, do we think the pluses outweigh the minuses?
On 7 September 2015 at 09:13, Stephen Connolly < [email protected]> wrote: > My main concern is that we do not introduce a build tool that makes it > even more complicated to build Jenkins behind a corporate firewall, as that > could significantly impact some of the contributors. > > While this is not something that personally affects me in my day job, it > would have made it extremely difficult to make my initial contributions > during the 2006-2011 period when I was behind a corporate firewall (absence > the hacking on public transport). > > On 7 September 2015 at 08:51, Robert Sandell <[email protected]> > wrote: > >> What about the existing adjunct support in stapler? >> That is meant to work as treating js, jelly et.al packages as maven >> modules. >> >> See for example https://github.com/stapler/stapler-adjunct-bootstrap, >> https://github.com/stapler/stapler-adjunct-jquery and >> https://github.com/stapler/stapler-adjunct-underscore >> >> /B >> >> On Sun, Sep 6, 2015 at 8:34 PM, Tom Fennelly <[email protected]> >> wrote: >> >>> Hi Surya. We're not inventing anything new for the bundling/packaging >>> part. It uses Browserify for that, which is similar to Webpack. >>> >>> So you are not against the idea of adding build steps to Jenkins core re >>> supporting modularised JavaScript? >>> >>> Sent from my iPhone >>> >>> On 6 Sep 2015, at 17:23, Surya Gaddipati <[email protected]> >>> wrote: >>> >>> Hi Tom, >>> >>> I've been packaging all kinds of js stuff with webpack. Avoids all kinds >>> of problems with globals ect that you described. >>> I am not quite sure if we need to invent a jenkins specific solution >>> here. >>> >>> Here is an example using elm >>> >>> https://github.com/DotCi/DotCiPipelineViewer >>> >>> example using react and co >>> >>> https://github.com/groupon/DotCi >>> >>> None of those leaks globals. >>> >>> Surya >>> >>> On Saturday, September 5, 2015 at 7:32:01 AM UTC-5, Tom Fennelly wrote: >>>> >>>> Something that might help ... a description of the state of JavaScript >>>> in Jenkins as we see it >>>> <https://github.com/tfennelly/jenkins-js-modules#problem--motivation>. >>>> >>> -- >>> 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/0wu31f3az_w/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/6948e86e-7313-44f9-93cd-ea6b42158093%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/6948e86e-7313-44f9-93cd-ea6b42158093%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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/0B84D67D-5876-4BFC-ACA7-DDEE85F817D2%40gmail.com >>> <https://groups.google.com/d/msgid/jenkinsci-dev/0B84D67D-5876-4BFC-ACA7-DDEE85F817D2%40gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Robert Sandell >> *Software Engineer* >> *CloudBees Inc.* >> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS2OYYm_1KFzpJgSLRc2TJcWqyQ9ULjAmmRzqMbwdpyuOw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS2OYYm_1KFzpJgSLRc2TJcWqyQ9ULjAmmRzqMbwdpyuOw%40mail.gmail.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 a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/0wu31f3az_w/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMwgccHVSq1BrKNjSJrxZRhKFbhzo0y6CYp%2BaYwG-05BKw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMwgccHVSq1BrKNjSJrxZRhKFbhzo0y6CYp%2BaYwG-05BKw%40mail.gmail.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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BbPaoLQpv_SEwbE7n-jX%2BU1U4TZ7rPD8EqAXz3DTMVHxdw0bw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
