If I follow the directions from https://github.com/jenkinsci/blueocean-plugin, here was my basic workflow.
git clone https://github.com/jenkinsci/blueocean-plugin cd blueocean-plugin mvn clean install mvn -f blueocean-plugin/pom.xml hpi:run I'm guessing I could skip most of the above development foo by starting with a recent 2.x build of Jenkins (war, rpm, or deb) & then add the experimental update site to get the newer plugins? On Thu, Jun 16, 2016 at 9:34 AM, Daniel Beck <[email protected]> wrote: > > > On 16.06.2016, at 16:29, Michael Madden <[email protected]> wrote: > > > > Wouldn't you have to still manually build the version of Jenkins from > https://github.com/jenkinsci/blueocean-plugin to get started. It sounds > like the experimental update site just updates plugins. > > Not sure what you mean. Blue Ocean is a set of regular Jenkins plugins, > requiring Jenkins 2.2 or newer AFAICT. > > -- > 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/FUQED3BAteg/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/DC8EB3E6-E437-4636-AE07-ACE09E3A6DA8%40beckweb.net > . > 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/CAF_Li0%3D1OS0KNqEoaCmEQhTtuj8W5Dvi8fXwmvAL4U8H7zbxRA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
