Re: [Blue Ocean] New UX project for jenkins

[Tom Fennelly]

On Thursday, June 2, 2016 at 7:03:17 PM UTC+1, Tom Fennelly wrote:
>
> We created a blueocean-acceptance-test 
>  repo and have 
> some initial acceptance/smoke tests in it.
>
> Hoping the repo can be moved to jenkinsci (HOSTING-109 
> ).
>
> Builds on the main acceptance-test-harness. Initial tests are written 
> using a JS selenium toolkit called Nightwatch.js 
> . There's a video on the README.md.
>

And of course this may end up being merged back into the  main 
acceptance-test-harness repo at some stage ... we'll see :)

-- 
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/39b659a6-35b9-4d28-8b7c-0380d9844fa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] New UX project for jenkins

[Tom Fennelly]

We created a blueocean-acceptance-test 
 repo and have some 
initial acceptance/smoke tests in it.

Hoping the repo can be moved to jenkinsci (HOSTING-109 
).

Builds on the main acceptance-test-harness. Initial tests are written using 
a JS selenium toolkit called Nightwatch.js . 
There's a video on the README.md.

-- 
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/9d2686ec-34af-4a5e-861a-c4543b994055%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] New UX project for jenkins

[Martin Reinhardt]

really cool

Am Montag, 30. Mai 2016 17:09:23 UTC+2 schrieb Surya Gaddipati:
>
> This is great work. Congrats. 
>
> SSE is nice touch that would make Jenkins so much more responsive. 
>
> On Thursday, May 26, 2016 at 5:44:06 PM UTC-5, Michael Neale wrote:
>>
>> I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the 
>> so-called "blueocean" plugin. 
>>
>> You may have heard this announced via the blog post 
>> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not, 
>> I'll give you a few minutes 
>>
>> to have a read... 
>>
>> Just kidding, who has time for that, let me explain. No, there is too 
>> much, let me sum up: 
>>
>> https://www.youtube.com/watch?v=GZYhDMCOyww
>>
>> (above is from the movie princess bride, more seriously, if you haven't 
>> seen this movie you really should, kind of urgently)
>>
>> Blue Ocean aims to be a plugin (well, a few moving parts delivered as 
>> plugins) that provides an extensible "next gen" user experience. Jenkins 
>> GUI has been around for 10 years now, and can be hard to extend and 
>> modernise (many of us have tried).
>>
>> Its initial focus is on "pipeline centric" and freestyle views for the 
>> busy developer, and is very much a work in progress. 
>>
>> The interesting bits for us developers: 
>>
>> Blue Ocean is based on ES6 
>> ,
>>  
>> Server Sent Events 
>> 
>>  
>> (realtime notifications), React.js 
>> 
>>  
>> for component model and gulp/npm  build chain, 
>> but wired in via the already in use jenkins-js modules 
>>  (this means there isn’t a need 
>> to be familiar with the whole js toolchain unless you want to be, and mvn 
>> install takes care of things normally). 
>>
>> Both client side (stuff in browser) and server side - are just Jenkins 
>> plugins. The server side uses the usual Jenkins web middleware (yes, 
>> stapler) and extensions/extension points. 
>>
>> A fair bit of head scratching was done to come up with an 
>> “” concept for blue ocean client side, however it was worth 
>> it as it means that plugins for the new UX can be delivered as normal 
>> Jenkins plugins but with js componentry. Jenkins serves up these plugins to 
>> the web browser so extension points in Blue Ocean pages can be fulfilled by 
>> any plugin offering those extensions (GUI extension points have names). 
>> This includes things like adding a new “route” for a new page to host a 
>> feature, or could be augmenting an existing page or component. A sample 
>> plugin and demo of it is here: 
>> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin. 
>>
>>
>> Extensions can be isolated in failure this way - so a bad bit of 
>> javascript doesn’t brick a whole page. 
>>
>> Blue Ocean when installed currently provides the new UX on the /blue top 
>> level route in Jenkins, so the classic GUI lives alongside it. The new GUI 
>> (markup, js) that is delivered via a fresh set of markup and JS bundles, so 
>> it doesn’t conflict with any existing GUI. 
>>
>> The UX model in blue ocean is more of a shift to what used to be called 
>> “client server” but is now a “single page app” (kind of), using pretty much 
>> standard React.js patterns (it is hoped that while React.js is the glue of 
>> blue ocean, plugin authors don’t have to be an expert in it, and could use 
>> something else to deliver their front end functionality). There is a server 
>> side API plugin called “blueocean-rest” which provides a http/REST-like api 
>> that helps drive the GUI (it too is extensible, but it just builds on stuff 
>> already in Jenkins) - it has a fairly neat README explaining the API as it 
>> is right now. You could describe this api as being a “BFF” pattern for the 
>> front end (see http://samnewman.io/patterns/architectural/bff/)
>>
>>
>> It’s still very early days obviously, but if you are interested take a 
>> look at https://github.com/cloudbees/blueocean (as soon as HOSTING 
>> ticket is resolved, development will move to the jenkinsci org’s fork of 
>> that repository). It’s a multi module project (blueocean-plugin is the 
>> aggregator). The “js-extensions” module is the middleware that makes the 
>> new ExtensionPoint stuff work. 
>>
>> There is also the https://github.com/cloudbees/jenkins-design-language 
>> repository (once again, will be forked into jenkinsci) which contains 
>> visual assets, reusable components and tries to codify a standard look/feel 
>> (what is a design language 
>> ). One thing front end 
>> developers have found useful when building components is storybook 
>> 

Re: [Blue Ocean] New UX project for jenkins

[Surya Gaddipati]

This is great work. Congrats. 

SSE is nice touch that would make Jenkins so much more responsive. 

On Thursday, May 26, 2016 at 5:44:06 PM UTC-5, Michael Neale wrote:
>
> I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the 
> so-called "blueocean" plugin. 
>
> You may have heard this announced via the blog post 
> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not, I'll 
> give you a few minutes 
>
> to have a read... 
>
> Just kidding, who has time for that, let me explain. No, there is too 
> much, let me sum up: 
>
> https://www.youtube.com/watch?v=GZYhDMCOyww
>
> (above is from the movie princess bride, more seriously, if you haven't 
> seen this movie you really should, kind of urgently)
>
> Blue Ocean aims to be a plugin (well, a few moving parts delivered as 
> plugins) that provides an extensible "next gen" user experience. Jenkins 
> GUI has been around for 10 years now, and can be hard to extend and 
> modernise (many of us have tried).
>
> Its initial focus is on "pipeline centric" and freestyle views for the 
> busy developer, and is very much a work in progress. 
>
> The interesting bits for us developers: 
>
> Blue Ocean is based on ES6 
> ,
>  
> Server Sent Events 
> 
>  
> (realtime notifications), React.js 
> 
>  
> for component model and gulp/npm  build chain, 
> but wired in via the already in use jenkins-js modules 
>  (this means there isn’t a need 
> to be familiar with the whole js toolchain unless you want to be, and mvn 
> install takes care of things normally). 
>
> Both client side (stuff in browser) and server side - are just Jenkins 
> plugins. The server side uses the usual Jenkins web middleware (yes, 
> stapler) and extensions/extension points. 
>
> A fair bit of head scratching was done to come up with an 
> “” concept for blue ocean client side, however it was worth 
> it as it means that plugins for the new UX can be delivered as normal 
> Jenkins plugins but with js componentry. Jenkins serves up these plugins to 
> the web browser so extension points in Blue Ocean pages can be fulfilled by 
> any plugin offering those extensions (GUI extension points have names). 
> This includes things like adding a new “route” for a new page to host a 
> feature, or could be augmenting an existing page or component. A sample 
> plugin and demo of it is here: 
> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin. 
>
> Extensions can be isolated in failure this way - so a bad bit of 
> javascript doesn’t brick a whole page. 
>
> Blue Ocean when installed currently provides the new UX on the /blue top 
> level route in Jenkins, so the classic GUI lives alongside it. The new GUI 
> (markup, js) that is delivered via a fresh set of markup and JS bundles, so 
> it doesn’t conflict with any existing GUI. 
>
> The UX model in blue ocean is more of a shift to what used to be called 
> “client server” but is now a “single page app” (kind of), using pretty much 
> standard React.js patterns (it is hoped that while React.js is the glue of 
> blue ocean, plugin authors don’t have to be an expert in it, and could use 
> something else to deliver their front end functionality). There is a server 
> side API plugin called “blueocean-rest” which provides a http/REST-like api 
> that helps drive the GUI (it too is extensible, but it just builds on stuff 
> already in Jenkins) - it has a fairly neat README explaining the API as it 
> is right now. You could describe this api as being a “BFF” pattern for the 
> front end (see http://samnewman.io/patterns/architectural/bff/)
>
>
> It’s still very early days obviously, but if you are interested take a 
> look at https://github.com/cloudbees/blueocean (as soon as HOSTING ticket 
> is resolved, development will move to the jenkinsci org’s fork of that 
> repository). It’s a multi module project (blueocean-plugin is the 
> aggregator). The “js-extensions” module is the middleware that makes the 
> new ExtensionPoint stuff work. 
>
> There is also the https://github.com/cloudbees/jenkins-design-language 
> repository (once again, will be forked into jenkinsci) which contains 
> visual assets, reusable components and tries to codify a standard look/feel 
> (what is a design language ). 
> One thing front end developers have found useful when building components 
> is storybook 
> .
>
>
>
>
> If you are interested in talking about this, we are using #jenkins-ux on 
> freenode irc (hopefully there is someone around most times), and also if 
> you post to this 

Re: [Blue Ocean] New UX project for jenkins

[Michael Neale]

FYI just did a "transfer of ownership" of the github repo to: 

https://github.com/jenkinsci/blueocean-plugin
https://github.com/jenkinsci/jenkins-design-language

old links redirect to there, and they are now fully operational. 

On Friday, May 27, 2016 at 8:44:06 AM UTC+10, Michael Neale wrote:
>
> I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the 
> so-called "blueocean" plugin. 
>
> You may have heard this announced via the blog post 
> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not, I'll 
> give you a few minutes 
>
> to have a read... 
>
> Just kidding, who has time for that, let me explain. No, there is too 
> much, let me sum up: 
>
> https://www.youtube.com/watch?v=GZYhDMCOyww
>
> (above is from the movie princess bride, more seriously, if you haven't 
> seen this movie you really should, kind of urgently)
>
> Blue Ocean aims to be a plugin (well, a few moving parts delivered as 
> plugins) that provides an extensible "next gen" user experience. Jenkins 
> GUI has been around for 10 years now, and can be hard to extend and 
> modernise (many of us have tried).
>
> Its initial focus is on "pipeline centric" and freestyle views for the 
> busy developer, and is very much a work in progress. 
>
> The interesting bits for us developers: 
>
> Blue Ocean is based on ES6 
> ,
>  
> Server Sent Events 
> 
>  
> (realtime notifications), React.js 
> 
>  
> for component model and gulp/npm  build chain, 
> but wired in via the already in use jenkins-js modules 
>  (this means there isn’t a need 
> to be familiar with the whole js toolchain unless you want to be, and mvn 
> install takes care of things normally). 
>
> Both client side (stuff in browser) and server side - are just Jenkins 
> plugins. The server side uses the usual Jenkins web middleware (yes, 
> stapler) and extensions/extension points. 
>
> A fair bit of head scratching was done to come up with an 
> “” concept for blue ocean client side, however it was worth 
> it as it means that plugins for the new UX can be delivered as normal 
> Jenkins plugins but with js componentry. Jenkins serves up these plugins to 
> the web browser so extension points in Blue Ocean pages can be fulfilled by 
> any plugin offering those extensions (GUI extension points have names). 
> This includes things like adding a new “route” for a new page to host a 
> feature, or could be augmenting an existing page or component. A sample 
> plugin and demo of it is here: 
> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin. 
>
> Extensions can be isolated in failure this way - so a bad bit of 
> javascript doesn’t brick a whole page. 
>
> Blue Ocean when installed currently provides the new UX on the /blue top 
> level route in Jenkins, so the classic GUI lives alongside it. The new GUI 
> (markup, js) that is delivered via a fresh set of markup and JS bundles, so 
> it doesn’t conflict with any existing GUI. 
>
> The UX model in blue ocean is more of a shift to what used to be called 
> “client server” but is now a “single page app” (kind of), using pretty much 
> standard React.js patterns (it is hoped that while React.js is the glue of 
> blue ocean, plugin authors don’t have to be an expert in it, and could use 
> something else to deliver their front end functionality). There is a server 
> side API plugin called “blueocean-rest” which provides a http/REST-like api 
> that helps drive the GUI (it too is extensible, but it just builds on stuff 
> already in Jenkins) - it has a fairly neat README explaining the API as it 
> is right now. You could describe this api as being a “BFF” pattern for the 
> front end (see http://samnewman.io/patterns/architectural/bff/)
>
>
> It’s still very early days obviously, but if you are interested take a 
> look at https://github.com/cloudbees/blueocean (as soon as HOSTING ticket 
> is resolved, development will move to the jenkinsci org’s fork of that 
> repository). It’s a multi module project (blueocean-plugin is the 
> aggregator). The “js-extensions” module is the middleware that makes the 
> new ExtensionPoint stuff work. 
>
> There is also the https://github.com/cloudbees/jenkins-design-language 
> repository (once again, will be forked into jenkinsci) which contains 
> visual assets, reusable components and tries to codify a standard look/feel 
> (what is a design language ). 
> One thing front end developers have found useful when building components 
> is storybook 
> .
>
>
>
>
> If you are interested in talking about 

Re: [Blue Ocean] New UX project for jenkins

[nicolas de loof]

yes indeed, see
https://github.com/jenkinsci/blueocean-plugin/pull/1/files/d14ffb3f68d4b21f76bd1b800fb74c5806e97db8#r64960271

2016-05-27 18:04 GMT+02:00 Tom Fennelly :

> I think Nicolas already has something cooked up and ready to go for this.
> We'll let you know when it's ready.
>
> On Friday, May 27, 2016 at 1:51:38 PM UTC+1, Stanislas Chollet wrote:
>>
>> Thanks James.
>>
>> I just created an issue on JIRA ->
>> https://issues.jenkins-ci.org/browse/JENKINS-35181
>>
>> Regards,
>>
>> On Friday, May 27, 2016 at 2:29:12 PM UTC+2, James Dumay wrote:
>>>
>>> We have a docker image that gets published daily to a private Docker
>>> repository but we need to move it to a public repository. Could you file an
>>> issue on JIRA with the Blue Ocean component?
>>> On Fri, May 27, 2016 at 10:27 PM, Stanislas Chollet <
>>> stanisla...@gmail.com> wrote:
>>>
 Hello Michael,

 Good job ! This new fresh UI is really a good improvement for the
 jenkins project !

 I wondering if there is a Docker image of Blue Ocean to try it directly
 on a existing installation ?

 Have a good day,

 On Friday, May 27, 2016 at 12:44:06 AM UTC+2, Michael Neale wrote:
>
> I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the
> so-called "blueocean" plugin.
>
> You may have heard this announced via the blog post
> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not,
> I'll give you a few minutes
>
> to have a read...
>
> Just kidding, who has time for that, let me explain. No, there is too
> much, let me sum up:
>
> https://www.youtube.com/watch?v=GZYhDMCOyww
>
> (above is from the movie princess bride, more seriously, if you
> haven't seen this movie you really should, kind of urgently)
>
> Blue Ocean aims to be a plugin (well, a few moving parts delivered as
> plugins) that provides an extensible "next gen" user experience. Jenkins
> GUI has been around for 10 years now, and can be hard to extend and
> modernise (many of us have tried).
>
> Its initial focus is on "pipeline centric" and freestyle views for the
> busy developer, and is very much a work in progress.
>
> The interesting bits for us developers:
>
> Blue Ocean is based on ES6
> ,
> Server Sent Events
> 
> (realtime notifications), React.js
> 
> for component model and gulp/npm  build
> chain, but wired in via the already in use jenkins-js modules
>  (this means there isn’t a
> need to be familiar with the whole js toolchain unless you want to be, and
> mvn install takes care of things normally).
>
> Both client side (stuff in browser) and server side - are just Jenkins
> plugins. The server side uses the usual Jenkins web middleware (yes,
> stapler) and extensions/extension points.
>
> A fair bit of head scratching was done to come up with an
> “” concept for blue ocean client side, however it was 
> worth
> it as it means that plugins for the new UX can be delivered as normal
> Jenkins plugins but with js componentry. Jenkins serves up these plugins 
> to
> the web browser so extension points in Blue Ocean pages can be fulfilled 
> by
> any plugin offering those extensions (GUI extension points have names).
> This includes things like adding a new “route” for a new page to host a
> feature, or could be augmenting an existing page or component. A sample
> plugin and demo of it is here:
> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin.
>
>
> Extensions can be isolated in failure this way - so a bad bit of
> javascript doesn’t brick a whole page.
>
> Blue Ocean when installed currently provides the new UX on the /blue
> top level route in Jenkins, so the classic GUI lives alongside it. The new
> GUI (markup, js) that is delivered via a fresh set of markup and JS
> bundles, so it doesn’t conflict with any existing GUI.
>
> The UX model in blue ocean is more of a shift to what used to be
> called “client server” but is now a “single page app” (kind of), using
> pretty much standard React.js patterns (it is hoped that while React.js is
> the glue of blue ocean, plugin authors don’t have to be an expert in it,
> and could use something else to deliver their front end functionality).
> There is a server side API plugin called “blueocean-rest” which provides a
> http/REST-like api that helps drive the GUI (it too is extensible, but it

Re: [Blue Ocean] New UX project for jenkins

['Manish Dubey' via Jenkins Developers]

Guys, appreciate if you suggeest me here. 


Best
Manish

On Friday, May 27, 2016 at 11:08:06 PM UTC+5:30, Manish Dubey wrote:

> Hello Michael,
>
> My bad if you are not the right person to ideate on below case. 
>
> Business case - 
>
> To develop a plugin for Continuous Integration Tools like Jenkins to 
> verify the changes made in Jenkins’ workspace between consecutive builds 
> and process further based on the changes.
>
>
> However since HANA as in this case does not have such a mechanism we need 
> the scan to triggered on daily or nightly basis irrespective of the changes 
> made or not.
>
>
> Can we develope a plugin which is executed once the Source Code from HANA 
> is loaded into the workspace of the Jenkins job, the plugin then goes 
> through the current workspace also retains a copy of previous workspace and 
> lets the job know if there is any change made so that the scan shall be 
> triggered only in case of change and thereby reducing the cost of unwanted 
> scans.
>
>
>
> Please ideate if this is the best-fit to go for plugin or  any best 
> available solution to avoid unwanted scans.
>
>
>
> Regards
>
> Manish
>
> On Friday, May 27, 2016 at 4:14:06 AM UTC+5:30, Michael Neale wrote:
>
>> I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the 
>> so-called "blueocean" plugin. 
>>
>> You may have heard this announced via the blog post 
>> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not, 
>> I'll give you a few minutes 
>>
>> to have a read... 
>>
>> Just kidding, who has time for that, let me explain. No, there is too 
>> much, let me sum up: 
>>
>> https://www.youtube.com/watch?v=GZYhDMCOyww
>>
>> (above is from the movie princess bride, more seriously, if you haven't 
>> seen this movie you really should, kind of urgently)
>>
>> Blue Ocean aims to be a plugin (well, a few moving parts delivered as 
>> plugins) that provides an extensible "next gen" user experience. Jenkins 
>> GUI has been around for 10 years now, and can be hard to extend and 
>> modernise (many of us have tried).
>>
>> Its initial focus is on "pipeline centric" and freestyle views for the 
>> busy developer, and is very much a work in progress. 
>>
>> The interesting bits for us developers: 
>>
>> Blue Ocean is based on ES6 
>> ,
>>  
>> Server Sent Events 
>> 
>>  
>> (realtime notifications), React.js 
>> 
>>  
>> for component model and gulp/npm  build chain, 
>> but wired in via the already in use jenkins-js modules 
>>  (this means there isn’t a need 
>> to be familiar with the whole js toolchain unless you want to be, and mvn 
>> install takes care of things normally). 
>>
>> Both client side (stuff in browser) and server side - are just Jenkins 
>> plugins. The server side uses the usual Jenkins web middleware (yes, 
>> stapler) and extensions/extension points. 
>>
>> A fair bit of head scratching was done to come up with an 
>> “” concept for blue ocean client side, however it was worth 
>> it as it means that plugins for the new UX can be delivered as normal 
>> Jenkins plugins but with js componentry. Jenkins serves up these plugins to 
>> the web browser so extension points in Blue Ocean pages can be fulfilled by 
>> any plugin offering those extensions (GUI extension points have names). 
>> This includes things like adding a new “route” for a new page to host a 
>> feature, or could be augmenting an existing page or component. A sample 
>> plugin and demo of it is here: 
>> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin. 
>>
>>
>> Extensions can be isolated in failure this way - so a bad bit of 
>> javascript doesn’t brick a whole page. 
>>
>> Blue Ocean when installed currently provides the new UX on the /blue top 
>> level route in Jenkins, so the classic GUI lives alongside it. The new GUI 
>> (markup, js) that is delivered via a fresh set of markup and JS bundles, so 
>> it doesn’t conflict with any existing GUI. 
>>
>> The UX model in blue ocean is more of a shift to what used to be called 
>> “client server” but is now a “single page app” (kind of), using pretty much 
>> standard React.js patterns (it is hoped that while React.js is the glue of 
>> blue ocean, plugin authors don’t have to be an expert in it, and could use 
>> something else to deliver their front end functionality). There is a server 
>> side API plugin called “blueocean-rest” which provides a http/REST-like api 
>> that helps drive the GUI (it too is extensible, but it just builds on stuff 
>> already in Jenkins) - it has a fairly neat README explaining the API as it 
>> is right now. You could describe this api as being a “BFF” pattern for 

Re: [Blue Ocean] New UX project for jenkins

['Manish Dubey' via Jenkins Developers]

Hello Michael,

My bad if you are not the right person to ideate on below case. 

Business case - 

To develop a plugin for Continuous Integration Tools like Jenkins to verify 
the changes made in Jenkins’ workspace between consecutive builds and 
process further based on the changes.


However since HANA as in this case does not have such a mechanism we need 
the scan to triggered on daily or nightly basis irrespective of the changes 
made or not.


Can we develope a plugin which is executed once the Source Code from HANA 
is loaded into the workspace of the Jenkins job, the plugin then goes 
through the current workspace also retains a copy of previous workspace and 
lets the job know if there is any change made so that the scan shall be 
triggered only in case of change and thereby reducing the cost of unwanted 
scans.



Please ideate if this is the best-fit to go for plugin or  any best 
available solution to avoid unwanted scans.



Regards

Manish

On Friday, May 27, 2016 at 4:14:06 AM UTC+5:30, Michael Neale wrote:

> I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the 
> so-called "blueocean" plugin. 
>
> You may have heard this announced via the blog post 
> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not, I'll 
> give you a few minutes 
>
> to have a read... 
>
> Just kidding, who has time for that, let me explain. No, there is too 
> much, let me sum up: 
>
> https://www.youtube.com/watch?v=GZYhDMCOyww
>
> (above is from the movie princess bride, more seriously, if you haven't 
> seen this movie you really should, kind of urgently)
>
> Blue Ocean aims to be a plugin (well, a few moving parts delivered as 
> plugins) that provides an extensible "next gen" user experience. Jenkins 
> GUI has been around for 10 years now, and can be hard to extend and 
> modernise (many of us have tried).
>
> Its initial focus is on "pipeline centric" and freestyle views for the 
> busy developer, and is very much a work in progress. 
>
> The interesting bits for us developers: 
>
> Blue Ocean is based on ES6 
> ,
>  
> Server Sent Events 
> 
>  
> (realtime notifications), React.js 
> 
>  
> for component model and gulp/npm  build chain, 
> but wired in via the already in use jenkins-js modules 
>  (this means there isn’t a need 
> to be familiar with the whole js toolchain unless you want to be, and mvn 
> install takes care of things normally). 
>
> Both client side (stuff in browser) and server side - are just Jenkins 
> plugins. The server side uses the usual Jenkins web middleware (yes, 
> stapler) and extensions/extension points. 
>
> A fair bit of head scratching was done to come up with an 
> “” concept for blue ocean client side, however it was worth 
> it as it means that plugins for the new UX can be delivered as normal 
> Jenkins plugins but with js componentry. Jenkins serves up these plugins to 
> the web browser so extension points in Blue Ocean pages can be fulfilled by 
> any plugin offering those extensions (GUI extension points have names). 
> This includes things like adding a new “route” for a new page to host a 
> feature, or could be augmenting an existing page or component. A sample 
> plugin and demo of it is here: 
> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin. 
>
> Extensions can be isolated in failure this way - so a bad bit of 
> javascript doesn’t brick a whole page. 
>
> Blue Ocean when installed currently provides the new UX on the /blue top 
> level route in Jenkins, so the classic GUI lives alongside it. The new GUI 
> (markup, js) that is delivered via a fresh set of markup and JS bundles, so 
> it doesn’t conflict with any existing GUI. 
>
> The UX model in blue ocean is more of a shift to what used to be called 
> “client server” but is now a “single page app” (kind of), using pretty much 
> standard React.js patterns (it is hoped that while React.js is the glue of 
> blue ocean, plugin authors don’t have to be an expert in it, and could use 
> something else to deliver their front end functionality). There is a server 
> side API plugin called “blueocean-rest” which provides a http/REST-like api 
> that helps drive the GUI (it too is extensible, but it just builds on stuff 
> already in Jenkins) - it has a fairly neat README explaining the API as it 
> is right now. You could describe this api as being a “BFF” pattern for the 
> front end (see http://samnewman.io/patterns/architectural/bff/)
>
>
> It’s still very early days obviously, but if you are interested take a 
> look at https://github.com/cloudbees/blueocean (as soon as HOSTING ticket 
> is resolved, development will 

Re: [Blue Ocean] New UX project for jenkins

[Stanislas Chollet]

Thanks James.

I just created an issue on JIRA 
-> https://issues.jenkins-ci.org/browse/JENKINS-35181

Regards,

On Friday, May 27, 2016 at 2:29:12 PM UTC+2, James Dumay wrote:
>
> We have a docker image that gets published daily to a private Docker 
> repository but we need to move it to a public repository. Could you file an 
> issue on JIRA with the Blue Ocean component?
> On Fri, May 27, 2016 at 10:27 PM, Stanislas Chollet  > wrote:
>
>> Hello Michael,
>>
>> Good job ! This new fresh UI is really a good improvement for the jenkins 
>> project !
>>
>> I wondering if there is a Docker image of Blue Ocean to try it directly 
>> on a existing installation ?
>>
>> Have a good day,
>>
>> On Friday, May 27, 2016 at 12:44:06 AM UTC+2, Michael Neale wrote:
>>>
>>> I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the 
>>> so-called "blueocean" plugin. 
>>>
>>> You may have heard this announced via the blog post 
>>> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not, 
>>> I'll give you a few minutes 
>>>
>>> to have a read... 
>>>
>>> Just kidding, who has time for that, let me explain. No, there is too 
>>> much, let me sum up: 
>>>
>>> https://www.youtube.com/watch?v=GZYhDMCOyww
>>>
>>> (above is from the movie princess bride, more seriously, if you haven't 
>>> seen this movie you really should, kind of urgently)
>>>
>>> Blue Ocean aims to be a plugin (well, a few moving parts delivered as 
>>> plugins) that provides an extensible "next gen" user experience. Jenkins 
>>> GUI has been around for 10 years now, and can be hard to extend and 
>>> modernise (many of us have tried).
>>>
>>> Its initial focus is on "pipeline centric" and freestyle views for the 
>>> busy developer, and is very much a work in progress. 
>>>
>>> The interesting bits for us developers: 
>>>
>>> Blue Ocean is based on ES6 
>>> ,
>>>  
>>> Server Sent Events 
>>> 
>>>  
>>> (realtime notifications), React.js 
>>> 
>>>  
>>> for component model and gulp/npm  build chain, 
>>> but wired in via the already in use jenkins-js modules 
>>>  (this means there isn’t a 
>>> need to be familiar with the whole js toolchain unless you want to be, and 
>>> mvn install takes care of things normally). 
>>>
>>> Both client side (stuff in browser) and server side - are just Jenkins 
>>> plugins. The server side uses the usual Jenkins web middleware (yes, 
>>> stapler) and extensions/extension points. 
>>>
>>> A fair bit of head scratching was done to come up with an 
>>> “” concept for blue ocean client side, however it was worth 
>>> it as it means that plugins for the new UX can be delivered as normal 
>>> Jenkins plugins but with js componentry. Jenkins serves up these plugins to 
>>> the web browser so extension points in Blue Ocean pages can be fulfilled by 
>>> any plugin offering those extensions (GUI extension points have names). 
>>> This includes things like adding a new “route” for a new page to host a 
>>> feature, or could be augmenting an existing page or component. A sample 
>>> plugin and demo of it is here: 
>>> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin. 
>>>
>>>
>>> Extensions can be isolated in failure this way - so a bad bit of 
>>> javascript doesn’t brick a whole page. 
>>>
>>> Blue Ocean when installed currently provides the new UX on the /blue top 
>>> level route in Jenkins, so the classic GUI lives alongside it. The new GUI 
>>> (markup, js) that is delivered via a fresh set of markup and JS bundles, so 
>>> it doesn’t conflict with any existing GUI. 
>>>
>>> The UX model in blue ocean is more of a shift to what used to be called 
>>> “client server” but is now a “single page app” (kind of), using pretty much 
>>> standard React.js patterns (it is hoped that while React.js is the glue of 
>>> blue ocean, plugin authors don’t have to be an expert in it, and could use 
>>> something else to deliver their front end functionality). There is a server 
>>> side API plugin called “blueocean-rest” which provides a http/REST-like api 
>>> that helps drive the GUI (it too is extensible, but it just builds on stuff 
>>> already in Jenkins) - it has a fairly neat README explaining the API as it 
>>> is right now. You could describe this api as being a “BFF” pattern for the 
>>> front end (see http://samnewman.io/patterns/architectural/bff/)
>>>
>>>
>>> It’s still very early days obviously, but if you are interested take a 
>>> look at https://github.com/cloudbees/blueocean (as soon as HOSTING 
>>> ticket is resolved, development will move to the jenkinsci org’s fork of 
>>> that repository). It’s a multi module project 

Re: [Blue Ocean] New UX project for jenkins

[James Dumay]

We have a docker image that gets published daily to a private Docker
repository but we need to move it to a public repository. Could you file an
issue on JIRA with the Blue Ocean component?
On Fri, May 27, 2016 at 10:27 PM, Stanislas Chollet <
stanislas.chol...@gmail.com> wrote:

> Hello Michael,
>
> Good job ! This new fresh UI is really a good improvement for the jenkins
> project !
>
> I wondering if there is a Docker image of Blue Ocean to try it directly on
> a existing installation ?
>
> Have a good day,
>
> On Friday, May 27, 2016 at 12:44:06 AM UTC+2, Michael Neale wrote:
>>
>> I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the
>> so-called "blueocean" plugin.
>>
>> You may have heard this announced via the blog post
>> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not,
>> I'll give you a few minutes
>>
>> to have a read...
>>
>> Just kidding, who has time for that, let me explain. No, there is too
>> much, let me sum up:
>>
>> https://www.youtube.com/watch?v=GZYhDMCOyww
>>
>> (above is from the movie princess bride, more seriously, if you haven't
>> seen this movie you really should, kind of urgently)
>>
>> Blue Ocean aims to be a plugin (well, a few moving parts delivered as
>> plugins) that provides an extensible "next gen" user experience. Jenkins
>> GUI has been around for 10 years now, and can be hard to extend and
>> modernise (many of us have tried).
>>
>> Its initial focus is on "pipeline centric" and freestyle views for the
>> busy developer, and is very much a work in progress.
>>
>> The interesting bits for us developers:
>>
>> Blue Ocean is based on ES6
>> ,
>> Server Sent Events
>> 
>> (realtime notifications), React.js
>> 
>> for component model and gulp/npm  build chain,
>> but wired in via the already in use jenkins-js modules
>>  (this means there isn’t a need
>> to be familiar with the whole js toolchain unless you want to be, and mvn
>> install takes care of things normally).
>>
>> Both client side (stuff in browser) and server side - are just Jenkins
>> plugins. The server side uses the usual Jenkins web middleware (yes,
>> stapler) and extensions/extension points.
>>
>> A fair bit of head scratching was done to come up with an
>> “” concept for blue ocean client side, however it was worth
>> it as it means that plugins for the new UX can be delivered as normal
>> Jenkins plugins but with js componentry. Jenkins serves up these plugins to
>> the web browser so extension points in Blue Ocean pages can be fulfilled by
>> any plugin offering those extensions (GUI extension points have names).
>> This includes things like adding a new “route” for a new page to host a
>> feature, or could be augmenting an existing page or component. A sample
>> plugin and demo of it is here:
>> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin.
>>
>>
>> Extensions can be isolated in failure this way - so a bad bit of
>> javascript doesn’t brick a whole page.
>>
>> Blue Ocean when installed currently provides the new UX on the /blue top
>> level route in Jenkins, so the classic GUI lives alongside it. The new GUI
>> (markup, js) that is delivered via a fresh set of markup and JS bundles, so
>> it doesn’t conflict with any existing GUI.
>>
>> The UX model in blue ocean is more of a shift to what used to be called
>> “client server” but is now a “single page app” (kind of), using pretty much
>> standard React.js patterns (it is hoped that while React.js is the glue of
>> blue ocean, plugin authors don’t have to be an expert in it, and could use
>> something else to deliver their front end functionality). There is a server
>> side API plugin called “blueocean-rest” which provides a http/REST-like api
>> that helps drive the GUI (it too is extensible, but it just builds on stuff
>> already in Jenkins) - it has a fairly neat README explaining the API as it
>> is right now. You could describe this api as being a “BFF” pattern for the
>> front end (see http://samnewman.io/patterns/architectural/bff/)
>>
>>
>> It’s still very early days obviously, but if you are interested take a
>> look at https://github.com/cloudbees/blueocean (as soon as HOSTING
>> ticket is resolved, development will move to the jenkinsci org’s fork of
>> that repository). It’s a multi module project (blueocean-plugin is the
>> aggregator). The “js-extensions” module is the middleware that makes the
>> new ExtensionPoint stuff work.
>>
>> There is also the https://github.com/cloudbees/jenkins-design-language
>> repository (once again, will be forked into jenkinsci) which contains
>> visual assets, reusable components and tries to codify a standard 

Re: [Blue Ocean] New UX project for jenkins

[Stanislas Chollet]

Hello Michael,

Good job ! This new fresh UI is really a good improvement for the jenkins 
project !

I wondering if there is a Docker image of Blue Ocean to try it directly on 
a existing installation ?

Have a good day,

On Friday, May 27, 2016 at 12:44:06 AM UTC+2, Michael Neale wrote:
>
> I just opened https://issues.jenkins-ci.org/browse/HOSTING-98 for the 
> so-called "blueocean" plugin. 
>
> You may have heard this announced via the blog post 
> https://jenkins.io//blog/2016/05/26/introducing-blue-ocean/. If not, I'll 
> give you a few minutes 
>
> to have a read... 
>
> Just kidding, who has time for that, let me explain. No, there is too 
> much, let me sum up: 
>
> https://www.youtube.com/watch?v=GZYhDMCOyww
>
> (above is from the movie princess bride, more seriously, if you haven't 
> seen this movie you really should, kind of urgently)
>
> Blue Ocean aims to be a plugin (well, a few moving parts delivered as 
> plugins) that provides an extensible "next gen" user experience. Jenkins 
> GUI has been around for 10 years now, and can be hard to extend and 
> modernise (many of us have tried).
>
> Its initial focus is on "pipeline centric" and freestyle views for the 
> busy developer, and is very much a work in progress. 
>
> The interesting bits for us developers: 
>
> Blue Ocean is based on ES6 
> ,
>  
> Server Sent Events 
> 
>  
> (realtime notifications), React.js 
> 
>  
> for component model and gulp/npm  build chain, 
> but wired in via the already in use jenkins-js modules 
>  (this means there isn’t a need 
> to be familiar with the whole js toolchain unless you want to be, and mvn 
> install takes care of things normally). 
>
> Both client side (stuff in browser) and server side - are just Jenkins 
> plugins. The server side uses the usual Jenkins web middleware (yes, 
> stapler) and extensions/extension points. 
>
> A fair bit of head scratching was done to come up with an 
> “” concept for blue ocean client side, however it was worth 
> it as it means that plugins for the new UX can be delivered as normal 
> Jenkins plugins but with js componentry. Jenkins serves up these plugins to 
> the web browser so extension points in Blue Ocean pages can be fulfilled by 
> any plugin offering those extensions (GUI extension points have names). 
> This includes things like adding a new “route” for a new page to host a 
> feature, or could be augmenting an existing page or component. A sample 
> plugin and demo of it is here: 
> https://github.com/cloudbees/blueocean-sample-pipeline-result-ext-plugin. 
>
> Extensions can be isolated in failure this way - so a bad bit of 
> javascript doesn’t brick a whole page. 
>
> Blue Ocean when installed currently provides the new UX on the /blue top 
> level route in Jenkins, so the classic GUI lives alongside it. The new GUI 
> (markup, js) that is delivered via a fresh set of markup and JS bundles, so 
> it doesn’t conflict with any existing GUI. 
>
> The UX model in blue ocean is more of a shift to what used to be called 
> “client server” but is now a “single page app” (kind of), using pretty much 
> standard React.js patterns (it is hoped that while React.js is the glue of 
> blue ocean, plugin authors don’t have to be an expert in it, and could use 
> something else to deliver their front end functionality). There is a server 
> side API plugin called “blueocean-rest” which provides a http/REST-like api 
> that helps drive the GUI (it too is extensible, but it just builds on stuff 
> already in Jenkins) - it has a fairly neat README explaining the API as it 
> is right now. You could describe this api as being a “BFF” pattern for the 
> front end (see http://samnewman.io/patterns/architectural/bff/)
>
>
> It’s still very early days obviously, but if you are interested take a 
> look at https://github.com/cloudbees/blueocean (as soon as HOSTING ticket 
> is resolved, development will move to the jenkinsci org’s fork of that 
> repository). It’s a multi module project (blueocean-plugin is the 
> aggregator). The “js-extensions” module is the middleware that makes the 
> new ExtensionPoint stuff work. 
>
> There is also the https://github.com/cloudbees/jenkins-design-language 
> repository (once again, will be forked into jenkinsci) which contains 
> visual assets, reusable components and tries to codify a standard look/feel 
> (what is a design language ). 
> One thing front end developers have found useful when building components 
> is storybook 
> .
>
>
>
>
> If you are interested in talking about this, we