The name mashup-portlets still fits quite well - they all fetch html from configured/scripted sources and display it in the portlet area.
I do not have a Jenkins account yet - who can create one for me? On Monday, December 16, 2013 8:37:20 PM UTC+11, Ullrich Hafner wrote: > > Yes, that sounds ok for me. Then Marco can put new portlets also into this > new plug-in. > > Is the name mashup-portlets still appropriate then? Or should the name > make more clear which portlets are part of this plugin? > > Every developer with IRC voice can fork your repository. You can create a > wiki page on your own (with your Jenkins account). > > Ulli > > Am 15.12.2013 um 23:31 schrieb Georg Henzler > <[email protected]<javascript:> > >: > > > I didn't know optional dependencies were possible. So I think then the > best way would be as follows: > > * Host the Jenkins Mashup Portlets at > https://github.com/jenkinsci<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fjenkinsci&sa=D&sntz=1&usg=AFQjCNFgLFBS-sCs7AgyJ7zbYqH_H8xk4g> > (my > github id is ghenzler, who can create the repository/wiki page for me?) > * Move the three Sonar portlets to > https://wiki.jenkins-ci.org/display/JENKINS/Sonar+plugin @Maintainers > (Evgeny, Simon, David & Julien): Have you had a look? > > -Georg > > On Friday, December 13, 2013 4:57:50 AM UTC+11, Ullrich Hafner wrote: >> >> You can make the dependency to the dashboard view optional. You can have >> a look at the findbugs plugin: here I'm providing some portlet's related to >> findbugs. If the user does not install the dashboard view, then the >> portlets just not show up, without causing a failure... >> >> Am Donnerstag, 12. Dezember 2013 schrieb Georg Henzler : >> >>> I think we cannot add the sonar portlets to the sonar plugin, because >>> that would introduce the dependency to the dashboard plugin (this would >>> mean forcing all users of the sonar plugin to install the dashboard >>> plugin). >>> >>> It would be an option to add the portlets to the dashboard view plugin - >>> on the other hand it probably gets at some point a bit monolistic if all >>> new portlets form the community end up in the dasboard view itself. >>> >>> @Peter & Marco: What do you think? >>> >>> Georg >>> >>> On Wednesday, December 11, 2013 11:16:57 PM UTC+11, Ullrich Hafner wrote: >>>> >>>> Wouldn’t it make more sense to add your core portlets to the dashboard >>>> view plug-in and add your sonar portlets to the sonar plugin? >>>> >>>> Ull >>>> >>>> Am 11.12.2013 um 03:24 schrieb Georg Henzler <[email protected]> >>>> : >>>> >>>> Hi all, >>>> >>>> I've created additional dashboard portlets to extend the >>>> https://wiki.jenkins-ci.org/display/JENKINS/Dashboard+View. They are >>>> very flexible (especially the Generic JS Portlet), but I have been using >>>> them mainly to create a Developer Dashboard that included the following >>>> information on one Jenkins page: >>>> >>>> * CI Build Status (obviously possible by default ;-)) >>>> * Latest SCM changes (using Recent Changes Portlet) >>>> * New Sonar Violations from last night's run (using the Sonar Portlets) >>>> * Server Status of DEV/TEST/INT (Deployment Job Status and current >>>> actual status using a Nagios-like URL for each server and the Generic JS >>>> Portlet to display the info) >>>> >>>> I believe nothing like this exists already (having checked >>>> https://wiki.jenkins-ci.org/display/JENKINS/Plugins) and I'd be happy >>>> to push it over to https://github.com/jenkinsci to make it available >>>> for everyone. >>>> >>>> For current source code and more information see >>>> https://github.com/ghenzler/jenkins-mashup-portlets >>>> >>>> Regards >>>> Georg >>>> >>>> >>>> -- >>>> 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 [email protected]. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> >>>> >>> -- >>> 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 [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> > -- > 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 [email protected] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
