Re: Infobox of plugin Wiki page missing

[Daniel Beck]

> On 17.06.2016, at 20:24, suresh kumar  wrote:
> 
> Yes my plugin wiki page also not showing information,
> https://wiki.jenkins-ci.org/display/JENKINS/File+Operations+Plugin
> Could you please help me out what needs to fixed to get back the info of the 
> plugin in wiki page.
> 

Your plugin's wiki page wasn't a child of the 'Plugins' wiki page, but of the 
'Hosting Plugins' wiki page.

I moved it, the plugin should reappear in the next few hours.

-- 
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/96D2C325-B0A6-41BE-A1FF-DE1291FE668A%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

[Blue Ocean] failed to write CommitId

[Marc Esher]

Hey all,

I've installed all the blue ocean hpis, and all dependencies, into an 
existing Jenkins 2.9 server running on RHEL.

Jenkins starts fine, and I get the "try blue ocean" button at the top of 
the screen.

However, when I go to /blue, I get "no pipelines found", and if I go to the 
XHR that failed (http://myjenkins/blue/rest/search/?q=type:pipeline), I see 
the following stack trace.

Any ideas?

thanks!

Marc




java.io.IOException: Failed to write commitId
 at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151)
 at org.kohsuke.stapler.export.Property.writeTo(Property.java:126)
 at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
 at org.kohsuke.stapler.export.Property.writeValue(Property.java:279)
 at org.kohsuke.stapler.export.Property.writeValue(Property.java:168)
 at org.kohsuke.stapler.export.Property.writeTo(Property.java:139)
 at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
 at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223)
 at org.kohsuke.stapler.export.Model.writeTo(Model.java:198)
 at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285)
 at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273)
 at hudson.model.Api.doJson(Api.java:211)
 at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.
generateResponse(PagedResponse.java:55)
 at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(
HttpResponseRenderer.java:124)
 at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(
HttpResponseRenderer.java:69)
 at org.kohsuke.stapler.Function.renderResponse(Function.java:119)
 at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java
:102)
 at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
 at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.
java:58)
 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
 at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380)
 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686)
 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
 at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380)
 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
 at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
 at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
 at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
 at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
ServletHandler.java:1669)
 at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
 at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.
doFilter(Endpoint.java:209)
 at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
 at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(
LessCSS.java:47)
 at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
 at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.
java:95)
 at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
 at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125)
 at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
 at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126)
 at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
ServletHandler.java:1652)
 at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
 at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
ServletHandler.java:1652)
 at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.
java:84)
 at hudson.security.UnwrapSecurityExceptionFilter.doFilter(
UnwrapSecurityExceptionFilter.java:51)
 at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.
java:87)
 at jenkins.security.ExceptionTranslationFilter.doFilter(
ExceptionTranslationFilter.java:117)
 at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.
java:87)
 at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter
(AnonymousProcessingFilter.java:125)
 at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.
java:87)
 at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(
RememberMeProcessingFilter.java:142)
 at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.
java:87)
 at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(
AbstractProcessingFilter.java:271)
 at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.
java:87)
 at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java
:93)

Re: Infobox of plugin Wiki page missing

[antonio . mansilla]

Hi Daniel,

thanks for your quick reply. I'll wait until next monday, let's check then 
if the changes were propagated or the problem is still there.

Am Freitag, 17. Juni 2016 15:57:25 UTC+2 schrieb Daniel Beck:
>
>
> > On 17.06.2016, at 15:15, antonio@flagbit.de  wrote: 
> > 
> > the plugin I'm maintainer is missing its infobox on the wiki page. It's 
> was always properly showed but since yesterday is not shown anymore. Is 
> anyone be able to show me the way to solve this? 
>
> The info box is fed from update site data. And in the current version, the 
> plugin is missing. I checked the generator log output, and it said: 
>
> > ** Wiki page does not exist, or is not a child of the Plugins wiki page: 
> https://wiki.jenkins-ci.org/display/JENKINS/Bitbucket+Cloud+Build+Status+Notifier+Plugin
>  
>
> However, I checked the current update center generator run, and your 
> plugin is in, so it should reappear once the change propagates. 
>
> Whether that was an actual problem with the wiki page, or whether the wiki 
> just was unavailable at the time, I don't know. 
>
>

-- 
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/8da7ec22-0075-4a24-840e-feaab81cdd9c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Infobox of plugin Wiki page missing

[Daniel Beck]

> On 17.06.2016, at 15:15, antonio.mansi...@flagbit.de wrote:
> 
> the plugin I'm maintainer is missing its infobox on the wiki page. It's was 
> always properly showed but since yesterday is not shown anymore. Is anyone be 
> able to show me the way to solve this?

The info box is fed from update site data. And in the current version, the 
plugin is missing. I checked the generator log output, and it said:

> ** Wiki page does not exist, or is not a child of the Plugins wiki page: 
> https://wiki.jenkins-ci.org/display/JENKINS/Bitbucket+Cloud+Build+Status+Notifier+Plugin

However, I checked the current update center generator run, and your plugin is 
in, so it should reappear once the change propagates.

Whether that was an actual problem with the wiki page, or whether the wiki just 
was unavailable at the time, I don't know.

-- 
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/37A5CDD5-392B-404A-9537-99DA4E36D299%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Infobox of plugin Wiki page missing

[antonio . mansilla]

I forgot to post the plugin github 
page https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin.

Am Freitag, 17. Juni 2016 15:15:11 UTC+2 schrieb antonio@flagbit.de:
>
> Hi guys,
>
> the plugin I'm maintainer is missing its infobox on the wiki page 
> .
>  
> It's was always properly showed but since yesterday is not shown anymore. 
> Is anyone be able to show me the way to solve this?
>
> Thanks and regards.
> Antonio Mansilla
>

-- 
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/69ba7b1d-ac57-4a36-bcc3-a453d751497f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Infobox of plugin Wiki page missing

[antonio . mansilla]

Hi guys,

the plugin I'm maintainer is missing its infobox on the wiki page 
.
 
It's was always properly showed but since yesterday is not shown anymore. 
Is anyone be able to show me the way to solve this?

Thanks and regards.
Antonio Mansilla

-- 
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/9ba42545-e263-43d3-9ed4-c08966f80c8c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin site overhaul?

[Slide]

I never said the current readme file would be used, just something that is
in the repo. It would be nice to be able to manage as much as possible from
the repo.

On Fri, Jun 17, 2016, 04:51 Baptiste Mathus  wrote:

> Thinking about it again, I somehow agree for the reasons above, and also
> probably because of legacy reasons:
>
> If we are to use the hundreds of already existing README, there's a good
> chance to see a lot of inconsistencies flowing through the documentation
> pipe...
>
>
> 2016-06-17 9:52 GMT+00:00 Adrien Lecharpentier <
> adrien.lecharpent...@gmail.com>:
>
>> I agree with Robert. Moreover, Readme files across the repositories are
>> not containing the same details, are not written the same way and some
>> repositories don't have any. I'm all for KISS principle but I don't think
>> README.md is the place to old this but it should be on the repository so
>> the maintainers have full control on it and users can offer fix /
>> enhancement on the doc through PR.
>>
>> Le ven. 17 juin 2016 à 11:24, Robert Sandell  a
>> écrit :
>>
>>> No please, how many times do I have to plead my case here?
>>> The readme in the root of the repo is IMO aimed at describing the
>>> repository you are currently looking at; e.g. what it is, *how to build
>>> it*, who maintains it, links to additional resources (like user docs)
>>> etc. it is not the user documentation, it is developer documentation.
>>>
>>> You should sync with the GSoC project that is currently going on user
>>> docs:
>>> https://groups.google.com/forum/#!searchin/jenkinsci-dev/GSoC/jenkinsci-dev/kNZMOsF_ueA/15BWeTdXDQAJ
>>>
>>> /B
>>>
>>> On Tue, Jun 14, 2016 at 10:43 PM, Gus Reiber 
>>> wrote:
>>>
 +1 to GitHub readme as well. Why put the same doc in 2 places.



 On Tuesday, June 14, 2016 at 1:30:24 PM UTC-7, slide wrote:
>
> +1 for the effort, ideally I'd like to see something that can pull
> information from the github README.md files and have people push updates 
> to
> the descriptions that would be shown to their own plugin repositories.
> Perhaps some of the other information could be pulled from a metadata file
> that was also in the plugin repository.
>
> On Tue, Jun 14, 2016 at 1:02 PM Gus Reiber 
> wrote:
>
>> Hey all,
>>So I have on and off pushed the idea that the Jenkins community
>> could benefit greatly from an overhaul of the wiki based plugins site. As
>> an ultimate goal, I don't see any reason we couldn't build something that
>> approach a modern app store, like https://play.google.com/store, but
>> for the short run, it seems like we should be able to improove upon the
>> browsing experience of the existing list page and detail view.
>>
>> Existing:
>>
>>- list: https://wiki.jenkins-ci.org/display/JENKINS/Plugins
>>- detail:
>>https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin
>>
>> I think as a minimum, we ought to be able to provide a reasonable
>> search interface and means of filtering plugins by maintainer, Jenkins 
>> core
>> requirement, plugins labels, and installation count. Plugins should also 
>> be
>> assigned to categories that map to Jenkins user expectations a bit better
>> than the current list of ~30ish maintainer assigned labels do today.
>> Ideally the user ought to be able to manage the list of all plugins by
>> specific features of the plugin and by some suggestion of quality or
>> currentness of the plugin.
>>
>> At various points, my interest in bringing this value to the
>> community has been great enough to assemble a couple of different
>> prototypes and wireframes, attempting to generate interest. I have also 
>> had
>> a chance to play with some prototypes from others all with what seems to 
>> me
>> to be reasonable implementation paths. Attached are a few more recent
>> sketches showing the gist of how we might handle searching and filtering 
>> as
>> well as the plugin details.
>>
>> Anyway, at the moment, the plugin site is maintained by our
>> representatives here in the community. So it is really the will of the
>> community that should be reflected in any efforts that are actually
>> deployed and later maintained by our community. Thus again, I am looking
>> for grass roots support for the effort, support that potentially includes
>> some avenue for long term hosting and support.
>>
>> So my questions are these: Is enhancing the plugin site really worth
>> that degree of effort to the community? If you think it is, would you be
>> willing to join the effort, both for the immediate development needs, but
>> also for longer term support? Do you have any experience with other
>> communities who manage to accomplish this sort of 

Re: Plugin site overhaul?

[Jesse Glick]

I have argued for getting rid of the “feature” of sucking in
`{excerpt}`s from the wiki for display in the update center (it is an
infrastructure headache), and I would likewise argue that a revamped
plugin list should obtain all of its metadata from the same source the
update center does, which should be plugin `*.hpi` files exclusively.
In other words, it does not matter where you host the plugin or how
you build it, so long as you conform to a documented file format and
publish to the specified artifact repository.

Now metadata could include _links_ to additional information (user
guides, etc.) which could live anywhere. Changelogs demand special
consideration, though: it is long-form content which really needs to
be in a machine-readable format so it can be displayed in different
modes. For example, if you are looking at the _Updates_ screen inside
Jenkins, you could click an expand button next to a plugin and see a
list of changes since the installed version.

-- 
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/CANfRfr0UQnCK-E_9aLiM46sQ6xeP0KBYYjNSjVMu8X-ecRH9xw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin site overhaul?

[Baptiste Mathus]

Thinking about it again, I somehow agree for the reasons above, and also
probably because of legacy reasons:

If we are to use the hundreds of already existing README, there's a good
chance to see a lot of inconsistencies flowing through the documentation
pipe...


2016-06-17 9:52 GMT+00:00 Adrien Lecharpentier <
adrien.lecharpent...@gmail.com>:

> I agree with Robert. Moreover, Readme files across the repositories are
> not containing the same details, are not written the same way and some
> repositories don't have any. I'm all for KISS principle but I don't think
> README.md is the place to old this but it should be on the repository so
> the maintainers have full control on it and users can offer fix /
> enhancement on the doc through PR.
>
> Le ven. 17 juin 2016 à 11:24, Robert Sandell  a
> écrit :
>
>> No please, how many times do I have to plead my case here?
>> The readme in the root of the repo is IMO aimed at describing the
>> repository you are currently looking at; e.g. what it is, *how to build
>> it*, who maintains it, links to additional resources (like user docs)
>> etc. it is not the user documentation, it is developer documentation.
>>
>> You should sync with the GSoC project that is currently going on user
>> docs:
>> https://groups.google.com/forum/#!searchin/jenkinsci-dev/GSoC/jenkinsci-dev/kNZMOsF_ueA/15BWeTdXDQAJ
>>
>> /B
>>
>> On Tue, Jun 14, 2016 at 10:43 PM, Gus Reiber 
>> wrote:
>>
>>> +1 to GitHub readme as well. Why put the same doc in 2 places.
>>>
>>>
>>>
>>> On Tuesday, June 14, 2016 at 1:30:24 PM UTC-7, slide wrote:

 +1 for the effort, ideally I'd like to see something that can pull
 information from the github README.md files and have people push updates to
 the descriptions that would be shown to their own plugin repositories.
 Perhaps some of the other information could be pulled from a metadata file
 that was also in the plugin repository.

 On Tue, Jun 14, 2016 at 1:02 PM Gus Reiber 
 wrote:

> Hey all,
>So I have on and off pushed the idea that the Jenkins community
> could benefit greatly from an overhaul of the wiki based plugins site. As
> an ultimate goal, I don't see any reason we couldn't build something that
> approach a modern app store, like https://play.google.com/store, but
> for the short run, it seems like we should be able to improove upon the
> browsing experience of the existing list page and detail view.
>
> Existing:
>
>- list: https://wiki.jenkins-ci.org/display/JENKINS/Plugins
>- detail:
>https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin
>
> I think as a minimum, we ought to be able to provide a reasonable
> search interface and means of filtering plugins by maintainer, Jenkins 
> core
> requirement, plugins labels, and installation count. Plugins should also 
> be
> assigned to categories that map to Jenkins user expectations a bit better
> than the current list of ~30ish maintainer assigned labels do today.
> Ideally the user ought to be able to manage the list of all plugins by
> specific features of the plugin and by some suggestion of quality or
> currentness of the plugin.
>
> At various points, my interest in bringing this value to the community
> has been great enough to assemble a couple of different prototypes and
> wireframes, attempting to generate interest. I have also had a chance to
> play with some prototypes from others all with what seems to me to be
> reasonable implementation paths. Attached are a few more recent sketches
> showing the gist of how we might handle searching and filtering as well as
> the plugin details.
>
> Anyway, at the moment, the plugin site is maintained by our
> representatives here in the community. So it is really the will of the
> community that should be reflected in any efforts that are actually
> deployed and later maintained by our community. Thus again, I am looking
> for grass roots support for the effort, support that potentially includes
> some avenue for long term hosting and support.
>
> So my questions are these: Is enhancing the plugin site really worth
> that degree of effort to the community? If you think it is, would you be
> willing to join the effort, both for the immediate development needs, but
> also for longer term support? Do you have any experience with other
> communities who manage to accomplish this sort of ends?
>
> ...and finally, could you help articulate a set of minimum
> requirements that would make overhauling the plugin site worth while?
>
> Thanks in advance,
> Gus
>
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop 

Re: Plugin site overhaul?

[Adrien Lecharpentier]

I agree with Robert. Moreover, Readme files across the repositories are not
containing the same details, are not written the same way and some
repositories don't have any. I'm all for KISS principle but I don't think
README.md is the place to old this but it should be on the repository so
the maintainers have full control on it and users can offer fix /
enhancement on the doc through PR.

Le ven. 17 juin 2016 à 11:24, Robert Sandell  a
écrit :

> No please, how many times do I have to plead my case here?
> The readme in the root of the repo is IMO aimed at describing the
> repository you are currently looking at; e.g. what it is, *how to build
> it*, who maintains it, links to additional resources (like user docs)
> etc. it is not the user documentation, it is developer documentation.
>
> You should sync with the GSoC project that is currently going on user
> docs:
> https://groups.google.com/forum/#!searchin/jenkinsci-dev/GSoC/jenkinsci-dev/kNZMOsF_ueA/15BWeTdXDQAJ
>
> /B
>
> On Tue, Jun 14, 2016 at 10:43 PM, Gus Reiber 
> wrote:
>
>> +1 to GitHub readme as well. Why put the same doc in 2 places.
>>
>>
>>
>> On Tuesday, June 14, 2016 at 1:30:24 PM UTC-7, slide wrote:
>>>
>>> +1 for the effort, ideally I'd like to see something that can pull
>>> information from the github README.md files and have people push updates to
>>> the descriptions that would be shown to their own plugin repositories.
>>> Perhaps some of the other information could be pulled from a metadata file
>>> that was also in the plugin repository.
>>>
>>> On Tue, Jun 14, 2016 at 1:02 PM Gus Reiber  wrote:
>>>
 Hey all,
So I have on and off pushed the idea that the Jenkins community
 could benefit greatly from an overhaul of the wiki based plugins site. As
 an ultimate goal, I don't see any reason we couldn't build something that
 approach a modern app store, like https://play.google.com/store, but
 for the short run, it seems like we should be able to improove upon the
 browsing experience of the existing list page and detail view.

 Existing:

- list: https://wiki.jenkins-ci.org/display/JENKINS/Plugins
- detail:
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin

 I think as a minimum, we ought to be able to provide a reasonable
 search interface and means of filtering plugins by maintainer, Jenkins core
 requirement, plugins labels, and installation count. Plugins should also be
 assigned to categories that map to Jenkins user expectations a bit better
 than the current list of ~30ish maintainer assigned labels do today.
 Ideally the user ought to be able to manage the list of all plugins by
 specific features of the plugin and by some suggestion of quality or
 currentness of the plugin.

 At various points, my interest in bringing this value to the community
 has been great enough to assemble a couple of different prototypes and
 wireframes, attempting to generate interest. I have also had a chance to
 play with some prototypes from others all with what seems to me to be
 reasonable implementation paths. Attached are a few more recent sketches
 showing the gist of how we might handle searching and filtering as well as
 the plugin details.

 Anyway, at the moment, the plugin site is maintained by our
 representatives here in the community. So it is really the will of the
 community that should be reflected in any efforts that are actually
 deployed and later maintained by our community. Thus again, I am looking
 for grass roots support for the effort, support that potentially includes
 some avenue for long term hosting and support.

 So my questions are these: Is enhancing the plugin site really worth
 that degree of effort to the community? If you think it is, would you be
 willing to join the effort, both for the immediate development needs, but
 also for longer term support? Do you have any experience with other
 communities who manage to accomplish this sort of ends?

 ...and finally, could you help articulate a set of minimum requirements
 that would make overhauling the plugin site worth while?

 Thanks in advance,
 Gus

 --
 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
 https://groups.google.com/d/msgid/jenkinsci-dev/33ab5051-e2b8-4684-8d9e-0d5aa6ab1284%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> 

Re: Plugin site overhaul?

[Robert Sandell]

No please, how many times do I have to plead my case here?
The readme in the root of the repo is IMO aimed at describing the
repository you are currently looking at; e.g. what it is, *how to build it*,
who maintains it, links to additional resources (like user docs) etc. it is
not the user documentation, it is developer documentation.

You should sync with the GSoC project that is currently going on user docs:
https://groups.google.com/forum/#!searchin/jenkinsci-dev/GSoC/jenkinsci-dev/kNZMOsF_ueA/15BWeTdXDQAJ

/B

On Tue, Jun 14, 2016 at 10:43 PM, Gus Reiber  wrote:

> +1 to GitHub readme as well. Why put the same doc in 2 places.
>
>
>
> On Tuesday, June 14, 2016 at 1:30:24 PM UTC-7, slide wrote:
>>
>> +1 for the effort, ideally I'd like to see something that can pull
>> information from the github README.md files and have people push updates to
>> the descriptions that would be shown to their own plugin repositories.
>> Perhaps some of the other information could be pulled from a metadata file
>> that was also in the plugin repository.
>>
>> On Tue, Jun 14, 2016 at 1:02 PM Gus Reiber  wrote:
>>
>>> Hey all,
>>>So I have on and off pushed the idea that the Jenkins community could
>>> benefit greatly from an overhaul of the wiki based plugins site. As an
>>> ultimate goal, I don't see any reason we couldn't build something that
>>> approach a modern app store, like https://play.google.com/store, but
>>> for the short run, it seems like we should be able to improove upon the
>>> browsing experience of the existing list page and detail view.
>>>
>>> Existing:
>>>
>>>- list: https://wiki.jenkins-ci.org/display/JENKINS/Plugins
>>>- detail: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin
>>>
>>> I think as a minimum, we ought to be able to provide a reasonable search
>>> interface and means of filtering plugins by maintainer, Jenkins core
>>> requirement, plugins labels, and installation count. Plugins should also be
>>> assigned to categories that map to Jenkins user expectations a bit better
>>> than the current list of ~30ish maintainer assigned labels do today.
>>> Ideally the user ought to be able to manage the list of all plugins by
>>> specific features of the plugin and by some suggestion of quality or
>>> currentness of the plugin.
>>>
>>> At various points, my interest in bringing this value to the community
>>> has been great enough to assemble a couple of different prototypes and
>>> wireframes, attempting to generate interest. I have also had a chance to
>>> play with some prototypes from others all with what seems to me to be
>>> reasonable implementation paths. Attached are a few more recent sketches
>>> showing the gist of how we might handle searching and filtering as well as
>>> the plugin details.
>>>
>>> Anyway, at the moment, the plugin site is maintained by our
>>> representatives here in the community. So it is really the will of the
>>> community that should be reflected in any efforts that are actually
>>> deployed and later maintained by our community. Thus again, I am looking
>>> for grass roots support for the effort, support that potentially includes
>>> some avenue for long term hosting and support.
>>>
>>> So my questions are these: Is enhancing the plugin site really worth
>>> that degree of effort to the community? If you think it is, would you be
>>> willing to join the effort, both for the immediate development needs, but
>>> also for longer term support? Do you have any experience with other
>>> communities who manage to accomplish this sort of ends?
>>>
>>> ...and finally, could you help articulate a set of minimum requirements
>>> that would make overhauling the plugin site worth while?
>>>
>>> Thanks in advance,
>>> Gus
>>>
>>> --
>>> 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
>>> https://groups.google.com/d/msgid/jenkinsci-dev/33ab5051-e2b8-4684-8d9e-0d5aa6ab1284%40googlegroups.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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/d8062fe5-ddd3-49b7-b530-6721ffa9243d%40googlegroups.com
> 
> .
>
> For more options, visit 

Re: [Blue Ocean] - blueocean ui not available

[James Dumay]

Best watch the blog and mailing lists - we will be announcing the availability 
of the plugin in the experimental update center in those location

-- 
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/f1bb0270-b886-4a5a-a83c-2b1ed2288293%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [blueocean-plugin] No pipelines found

[James Dumay]

Great to hear that you found a resolution. Restart has tripped me up a few 
times too.

-- 
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/8144563e-b48b-4575-a4ec-800e731965af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.