Moving this thread to the Developer Mailing list

On Monday, March 11, 2019 at 6:54:49 AM UTC+1, Parichay Barpanda wrote:
>
> Hi all,
>
> I was going through the Plugin tutorial 
> <https://wiki.jenkins.io/display/JENKINS/Plugin+tutorial> page from 
> Jenkins Wiki. There is a nice description of *how to setup a skeleton 
> plugin for development of Jenkins Classic*. 
>
> For creating a skeleton plugin for Blue Ocean, the page recommends to see 
> the generator-blueocean-usain 
> <https://www.npmjs.com/package/generator-blueocean-usain> Yeoman 
> generator. I tried setting it up on my local machine but got stuck with 
> some errors. I have raised an issue on their GitHub repository. The best is 
> to see the GitHub issue as it can be better described in a markdown editor. 
> So, attaching the link to the issue - 
> https://github.com/tfennelly/generator-blueocean-usain/issues/2
>
> If anyone having experience with Blueocean development, let me know if you 
> can suggest a workaround or the reason for this error.
>
> Another question is to the Blueocean developers, 
>
> How do you prefer to setup your environment to start the developing for a 
> BlueOcean plugin? Jenkins Wiki Page on Blueocean Plugin Dev 
> <https://jenkins.io/doc/developer/blueocean-plugin-development/> also 
> suggests to Take a look at a real plugin (non trivial)* - *visual 
> pipeline editor 
> <https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-pipeline-editor>*,
>  
> *does it mean that we edit the plugin to form a skeleton of Blueocean 
> plugin?
>
> Thank you.
>
> Regards,
> Parichay (aka baymac)
>

-- 
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/abe64cd9-31d8-4b31-8ce1-27597b4d856b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to