Re: Infobox of plugin Wiki page missing

> 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

[Blue Ocean] failed to write CommitId

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

Re: Infobox of plugin Wiki page missing

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

Re: Infobox of plugin Wiki page missing

> 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

Re: Infobox of plugin Wiki page missing

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 >

Infobox of plugin Wiki page missing

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?

Re: Plugin site overhaul?

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

Re: Plugin site overhaul?

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

Re: Plugin site overhaul?

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

Re: Plugin site overhaul?

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

Re: Plugin site overhaul?

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

Re: [Blue Ocean] - blueocean ui not available

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

Re: [blueocean-plugin] No pipelines found

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