Blue Ocean for developers

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Blue Ocean for developers

Ulli Hafner
Is blue ocean ready for plug-in authors? Or is the API still in flow?
I found two empty pages in the wiki:
https://wiki.jenkins.io/display/JENKINS/Making+your+plugin+work+with+blue+ocean
https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+development
So I’m wondering if it makes sense to start to look at the current state from a developers perspective?
Or should I wait for more things (and documentation) to come? Is there a good starting point for developers available?
Or should I fork https://github.com/jenkinsci/blueocean-plugin and start to look at the code and documentation there?

Sorry for so many questions but I’m just not sure if I already should spend time in that quite interesting new part of Jenkins…



--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (506 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Blue Ocean for developers

Keith Zantow-2
Hi Ullrich,

I hope not to overstep my bounds, but I would like to say a few things:

1) Blue Ocean is currently extensible, there is an extensibility mechanism described in the README
2) there is some ongoing work to provide a simpler and more type safe method of extending Blue Ocean, which will likely land before 2018

I'm not sure of your needs, but holding off for just a bit might be wise.

Thanks,
-Keith

On Fri, Oct 13, 2017 at 10:55 AM, Ullrich Hafner <[hidden email]> wrote:
Is blue ocean ready for plug-in authors? Or is the API still in flow?
I found two empty pages in the wiki:
https://wiki.jenkins.io/display/JENKINS/Making+your+plugin+work+with+blue+ocean
https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+development
So I’m wondering if it makes sense to start to look at the current state from a developers perspective?
Or should I wait for more things (and documentation) to come? Is there a good starting point for developers available?
Or should I fork https://github.com/jenkinsci/blueocean-plugin and start to look at the code and documentation there?

Sorry for so many questions but I’m just not sure if I already should spend time in that quite interesting new part of Jenkins…



--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Blue Ocean for developers

Kohsuke Kawaguchi
Administrator
This is one of the topics I'm really keen on. Needless to say, it's incredibly important for plugins to be able to extend Blue Ocean just like they can Jenkins.

I've seen some of the stuff Keith has been working on, and I'm really looking forward to those.

On Fri, Oct 13, 2017 at 9:40 AM Keith Zantow <[hidden email]> wrote:
Hi Ullrich,

I hope not to overstep my bounds, but I would like to say a few things:

1) Blue Ocean is currently extensible, there is an extensibility mechanism described in the README
2) there is some ongoing work to provide a simpler and more type safe method of extending Blue Ocean, which will likely land before 2018

I'm not sure of your needs, but holding off for just a bit might be wise.

Thanks,
-Keith

On Fri, Oct 13, 2017 at 10:55 AM, Ullrich Hafner <[hidden email]> wrote:
Is blue ocean ready for plug-in authors? Or is the API still in flow?
I found two empty pages in the wiki:
https://wiki.jenkins.io/display/JENKINS/Making+your+plugin+work+with+blue+ocean
https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+development
So I’m wondering if it makes sense to start to look at the current state from a developers perspective?
Or should I wait for more things (and documentation) to come? Is there a good starting point for developers available?
Or should I fork https://github.com/jenkinsci/blueocean-plugin and start to look at the code and documentation there?

Sorry for so many questions but I’m just not sure if I already should spend time in that quite interesting new part of Jenkins…



--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
Kohsuke Kawaguchi

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yBw3r5y6sSKwr_3xfygAjj%3D3VGx8htzGFWBguJ7pMa4Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Blue Ocean for developers

Jesse Glick-4
On Fri, Oct 13, 2017 at 1:48 PM, Kohsuke Kawaguchi <[hidden email]> wrote:
> it's
> incredibly important for plugins to be able to extend Blue Ocean just like
> they can Jenkins.

Someone needs to take over

https://github.com/jenkinsci/archetypes/pull/24

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr33MOEPGsqWO2w_0sHUBFH3Zc8uu7chCya1X_CiqqLH-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Blue Ocean for developers

Kanstantsin Shautsou-2
In reply to this post by Kohsuke Kawaguchi
Waiting for 1 year for any information about non better (non jelly) UIs in jenkins for non workflow job types and other plugins. My impression is that jenkins is totally locked with hard deps to workflow job type today. Huge blueocean repo with model duplicates outside of plugin code is not something that we expect for development/usage.

On Friday, October 13, 2017 at 8:49:02 PM UTC+3, Kohsuke Kawaguchi wrote:
This is one of the topics I'm really keen on. Needless to say, it's incredibly important for plugins to be able to extend Blue Ocean just like they can Jenkins.

I've seen some of the stuff Keith has been working on, and I'm really looking forward to those.

On Fri, Oct 13, 2017 at 9:40 AM Keith Zantow <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="2qr8LBtLAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">kza...@...> wrote:
Hi Ullrich,

I hope not to overstep my bounds, but I would like to say a few things:

1) Blue Ocean is currently extensible, there is an extensibility mechanism described in the README
2) there is some ongoing work to provide a simpler and more type safe method of extending Blue Ocean, which will likely land before 2018

I'm not sure of your needs, but holding off for just a bit might be wise.

Thanks,
-Keith

On Fri, Oct 13, 2017 at 10:55 AM, Ullrich Hafner <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="2qr8LBtLAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ullrich...@...> wrote:
Is blue ocean ready for plug-in authors? Or is the API still in flow?
I found two empty pages in the wiki:
<a href="https://wiki.jenkins.io/display/JENKINS/Making+your+plugin+work+with+blue+ocean" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FMaking%2Byour%2Bplugin%2Bwork%2Bwith%2Bblue%2Bocean\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHaL_VdA86jYE2Ol1fVYKTk4dPPOg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FMaking%2Byour%2Bplugin%2Bwork%2Bwith%2Bblue%2Bocean\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHaL_VdA86jYE2Ol1fVYKTk4dPPOg&#39;;return true;">https://wiki.jenkins.io/display/JENKINS/Making+your+plugin+work+with+blue+ocean
<a href="https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+development" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FBlue%2BOcean%2Bdevelopment\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGbVnHNloagbuGvb3SY7LMigmHsaA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FBlue%2BOcean%2Bdevelopment\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGbVnHNloagbuGvb3SY7LMigmHsaA&#39;;return true;">https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+development
So I’m wondering if it makes sense to start to look at the current state from a developers perspective?
Or should I wait for more things (and documentation) to come? Is there a good starting point for developers available?
Or should I fork <a href="https://github.com/jenkinsci/blueocean-plugin" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fblueocean-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHUxPoY5Ev1AasHB-6yru9OW_Q02Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fblueocean-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHUxPoY5Ev1AasHB-6yru9OW_Q02Q&#39;;return true;">https://github.com/jenkinsci/blueocean-plugin and start to look at the code and documentation there?

Sorry for so many questions but I’m just not sure if I already should spend time in that quite interesting new part of Jenkins…



--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="2qr8LBtLAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="2qr8LBtLAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.
--
Kohsuke Kawaguchi

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c1da530f-5a1e-47db-8fd2-72b9b94a1164%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Blue Ocean for developers

Kanstantsin Shautsou-2
s/non//

On Saturday, October 14, 2017 at 9:04:31 PM UTC+3, Kanstantsin Shautsou wrote:
Waiting for 1 year for any information about non better (non jelly) UIs in jenkins for non workflow job types and other plugins. My impression is that jenkins is totally locked with hard deps to workflow job type today. Huge blueocean repo with model duplicates outside of plugin code is not something that we expect for development/usage.

On Friday, October 13, 2017 at 8:49:02 PM UTC+3, Kohsuke Kawaguchi wrote:
This is one of the topics I'm really keen on. Needless to say, it's incredibly important for plugins to be able to extend Blue Ocean just like they can Jenkins.

I've seen some of the stuff Keith has been working on, and I'm really looking forward to those.

On Fri, Oct 13, 2017 at 9:40 AM Keith Zantow <[hidden email]> wrote:
Hi Ullrich,

I hope not to overstep my bounds, but I would like to say a few things:

1) Blue Ocean is currently extensible, there is an extensibility mechanism described in the README
2) there is some ongoing work to provide a simpler and more type safe method of extending Blue Ocean, which will likely land before 2018

I'm not sure of your needs, but holding off for just a bit might be wise.

Thanks,
-Keith

On Fri, Oct 13, 2017 at 10:55 AM, Ullrich Hafner <[hidden email]> wrote:
Is blue ocean ready for plug-in authors? Or is the API still in flow?
I found two empty pages in the wiki:
<a href="https://wiki.jenkins.io/display/JENKINS/Making+your+plugin+work+with+blue+ocean" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FMaking%2Byour%2Bplugin%2Bwork%2Bwith%2Bblue%2Bocean\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHaL_VdA86jYE2Ol1fVYKTk4dPPOg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FMaking%2Byour%2Bplugin%2Bwork%2Bwith%2Bblue%2Bocean\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHaL_VdA86jYE2Ol1fVYKTk4dPPOg&#39;;return true;">https://wiki.jenkins.io/display/JENKINS/Making+your+plugin+work+with+blue+ocean
<a href="https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+development" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FBlue%2BOcean%2Bdevelopment\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGbVnHNloagbuGvb3SY7LMigmHsaA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FBlue%2BOcean%2Bdevelopment\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGbVnHNloagbuGvb3SY7LMigmHsaA&#39;;return true;">https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+development
So I’m wondering if it makes sense to start to look at the current state from a developers perspective?
Or should I wait for more things (and documentation) to come? Is there a good starting point for developers available?
Or should I fork <a href="https://github.com/jenkinsci/blueocean-plugin" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fblueocean-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHUxPoY5Ev1AasHB-6yru9OW_Q02Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fblueocean-plugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHUxPoY5Ev1AasHB-6yru9OW_Q02Q&#39;;return true;">https://github.com/jenkinsci/blueocean-plugin and start to look at the code and documentation there?

Sorry for so many questions but I’m just not sure if I already should spend time in that quite interesting new part of Jenkins…



--
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-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.
--
Kohsuke Kawaguchi

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/61dae4d9-8c63-4827-9cb8-d2834d21ec80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Blue Ocean for developers

Ulli Hafner
In reply to this post by Kohsuke Kawaguchi
Ok, thanks for the feedback. Then I will wait a litte bit longer…

Maybe a related question: since blue ocean will not support freestyle jobs (but freestyle jobs will hopefully be still supported in Jenkins in the future).
Are there recommendations of the blue ocean team on modern Java script libraries that plug-in authors should use in plugins? (Otherwise new freestyle UIs will again need a heavy refactoring in order to get it into blue ocean). 
E.g., YUI is dead, but no alternative has been suggested for Jenkins yet. Wouldn’t it make sense to provide at least some recommendations, so that the plug-in ecosystem will not diverge (and there are sooo many new libraries).
Or is the set of libraries in https://github.com/jenkinsci/js-libs a good starting point? 

Am 13.10.2017 um 19:48 schrieb Kohsuke Kawaguchi <[hidden email]>:

This is one of the topics I'm really keen on. Needless to say, it's incredibly important for plugins to be able to extend Blue Ocean just like they can Jenkins.

I've seen some of the stuff Keith has been working on, and I'm really looking forward to those.

On Fri, Oct 13, 2017 at 9:40 AM Keith Zantow <[hidden email]> wrote:
Hi Ullrich,

I hope not to overstep my bounds, but I would like to say a few things:

1) Blue Ocean is currently extensible, there is an extensibility mechanism described in the README
2) there is some ongoing work to provide a simpler and more type safe method of extending Blue Ocean, which will likely land before 2018

I'm not sure of your needs, but holding off for just a bit might be wise.

Thanks,
-Keith

On Fri, Oct 13, 2017 at 10:55 AM, Ullrich Hafner <[hidden email]> wrote:
Is blue ocean ready for plug-in authors? Or is the API still in flow?
I found two empty pages in the wiki:
https://wiki.jenkins.io/display/JENKINS/Making+your+plugin+work+with+blue+ocean
https://wiki.jenkins.io/display/JENKINS/Blue+Ocean+development
So I’m wondering if it makes sense to start to look at the current state from a developers perspective?
Or should I wait for more things (and documentation) to come? Is there a good starting point for developers available?
Or should I fork https://github.com/jenkinsci/blueocean-plugin and start to look at the code and documentation there?

Sorry for so many questions but I’m just not sure if I already should spend time in that quite interesting new part of Jenkins…



--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/870B1CCB-3FCE-45E4-8951-FD65F3090D89%40gmail.com.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJTHQaHq25xTRMTy7SfqF19D0RT3KJuMGcqv032NchYZL%2BXRtg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
Kohsuke Kawaguchi

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yBw3r5y6sSKwr_3xfygAjj%3D3VGx8htzGFWBguJ7pMa4Q%40mail.gmail.com.
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/F2617960-FD61-4FEE-8350-180D9D7DCF43%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

signature.asc (540 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Blue Ocean for developers

Jesse Glick-4
On Sat, Nov 4, 2017 at 12:59 PM, Ullrich Hafner
<[hidden email]> wrote:
> blue ocean will not support freestyle jobs

AFAIK B.O. supports basic display of freestyle builds.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr2KgFm_zrLz4qU03EjXBFfs1Vyrc7orUmMsqnxgiYRGHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.