Re: wiki page for Chat Room jenkins plugin
On 30.04.2015, at 02:26, Richard Bywater rich...@byh2o.com wrote: Not sure if I'm the only one who has this concern (or even if its a valid concern), but it seems rather easy for someone to easily stick any old plugin into the update centre. Is there a potential that someone could load up nefarious plugins that trick users into installing them and having them do bad things? (Yes you could do that to any of the plugins that currently exist but at least there's some track of stuff in Github - well, mostly - for JenkinsCI org-hosted ones anyway) I am also concerned about this. I doubt any of our users expect this to even be possible, it is so ludicrous. It'd be trivial for any of several hundred users to upload a patched Email-ext or Maven plugin and get a few thousand installs before we even notice. This is one of the reasons I want us to require that plugins need to be released from jenkinsci repos. It should be fairly straightforward to match release tags to plugin releases, and if the tag is missing, we don't publish a release in the UC. And if not everyone were in the 'Everyone' group with write access to every plugin repo by default [1], we could even ensure that the user who released the artifact is (or was at the time the plugin was released) in fact one of the plugin committers. We already have a 'Github ID' field in LDAP/the account app, so this could be matched automatically. Neither of these would be 100% safe, but I expect that this would make it much more difficult to upload any artifact and have it actually distributed. We're not an 'App Store', we don't vet what we offer. But preventing the most obvious ways to exploit the update center should be shut down. 1: There is nothing wrong with giving users permissions like that when they ask for it (and maybe explain why they want it), but let's not do this by default. 400 people have push (--force) privileges to 1200 repos. What could possibly go wrong?! -- 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/A47D3F53-CCC7-438C-B9F0-415FB088A479%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins Chat Room Plugin
According to the Update Centre, the developer ID is nicolas, which
from looking at other plugins seems to be ndeloof?
The artifact ID is cloudbees-disk-usage-simple, the source is nowhere
to be found, and there's no wiki page.
Unfortunately, this seems to be a common occurrence for plugins
associated with this developer ID — from eight plugins in the Update
Centre, only one has a wiki page with a valid infobox:
curl -s -L
https://updates.jenkins-ci.org/current/update-center.json | tail -n +2 |
head -n -1 | jq '.plugins[] | select(.developers[].developerId ==
nicolas) | {artifact: .name, name: .title, pubDate: .buildDate, wiki:
.wiki }'
In other words, hiding plugins without a wiki page would be a good idea :)
This also lends more credence to the argument that all plugins in the
Update Centre should be hosted under the jenkinsci GitHub organisation.
Regards,
Chris
On 30/04/15 17:50, Baptiste Mathus wrote:
For example: what's this:
https://twitter.com/jenkins_release/status/593756206839173120
+1 to just make those plugins invisible until they fix those things.
From my experience, the soft behaviour just does not work. Plugins
developers will only fix their plugin if it prevents them from being
publicly visible/usable.
And users will still /suffer/ from this. The requirement we're talking
is not much IMO.
Or, maybe we could just require having some file inside the repository
itself?
2015-04-28 20:36 GMT+02:00 Oleg Nenashev o.v.nenas...@gmail.com
mailto:o.v.nenas...@gmail.com:
I would alter the UC's behavior in order to consider plugins as
deprecated if there's no Wiki pages for them (probably with an extra
whitelist based in jenkins-infra) with a minimal standardised set of
sections (extra macros to poll poms?).
BR, Oleg
понедельник, 27 апреля 2015 г., 23:51:56 UTC+3 пользователь Daniel
Beck написал:
On 27.04.2015, at 13:36, Christopher Orr ch...@orr.me.uk wrote:
It is possible to edit the ignores file in the update centre code
[2], but that requires a pull request and getting somebody to merge it etc.
They can easily be created within a minute or two on the Github
UI, and I'd be happy to review and merge any such PR. (My open
PR was mainly to allow community review, I could have committed
it directly.)
--
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
mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.
--
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
--
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
mailto:jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4xwReo3_pZgMugY4R1_H5TCuoQnftYn3nFRUQRJ5CdTQ%40mail.gmail.com
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS4xwReo3_pZgMugY4R1_H5TCuoQnftYn3nFRUQRJ5CdTQ%40mail.gmail.com?utm_medium=emailutm_source=footer.
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/55425893.5060300%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.
Out of disk space error on system partition: Can temp location for file parameter upload be changed?
I discovered that on a Windows Jenkins server (Windows 2008 R2 Server) when a 'file parameter uploads a file to the server it uses the * C:\Users\userName\AppData\Local\Temp* folder to keep a temporary copy of the file. In addition, these temporary files are not cleaned with any frequency. As a result, I have run out of disk space trying to upload large files to the server. However, the same server has a very large D partition. Is it possible to redirect the temporary file parameter uploads to this partition instead of the C system partition? Thanks for any feedback! Ioannis -- 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/45f995a1-a5e4-458c-ac90-a95c8de47ad1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Hosting request for Exactor plugin
Hi, Exactor is a framework for writing automated acceptance tests of the kind advocated by Extreme Programming. I've developed a Jenkins plugin that exposes html reports generated by Exactor at the end of every build. Plugin name: Exactor Jenkins Github id: adelolmo Github url: https://github.com/adelolmo/exactor-jenkins Should the plugin name be changed ?? Something without jenkins on it ?? Thank you, Andoni https://github.com/ChaitanyaChannella/BehaveResultsJenkinsPlugin -- 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/ff5b22d7-feec-47cb-86cf-976adf598556%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Hosting request for Exactor plugin
Forgot to add some links about Exactor. https://code.google.com/p/exactor/ https://github.com/mlieshoff/exactor On Thursday, 30 April 2015 20:53:57 UTC+2, Andoni del Olmo wrote: Hi, Exactor is a framework for writing automated acceptance tests of the kind advocated by Extreme Programming. I've developed a Jenkins plugin that exposes html reports generated by Exactor at the end of every build. Plugin name: Exactor Jenkins Github id: adelolmo Github url: https://github.com/adelolmo/exactor-jenkins Should the plugin name be changed ?? Something without jenkins on it ?? Thank you, Andoni https://github.com/ChaitanyaChannella/BehaveResultsJenkinsPlugin -- 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/b6bd6430-eb12-43c3-a876-6a79d78a574b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Hosting request for Exactor plugin
How does your plugin differ from the HTML Publisher plugin as you mention that the tool spits out HTML reports? Richard On 7:02AM, Fri, 1/05/2015 Andoni del Olmo andoni.delo...@gmail.com wrote: Forgot to add some links about Exactor. https://code.google.com/p/exactor/ https://github.com/mlieshoff/exactor On Thursday, 30 April 2015 20:53:57 UTC+2, Andoni del Olmo wrote: Hi, Exactor is a framework for writing automated acceptance tests of the kind advocated by Extreme Programming. I've developed a Jenkins plugin that exposes html reports generated by Exactor at the end of every build. Plugin name: Exactor Jenkins Github id: adelolmo Github url: https://github.com/adelolmo/exactor-jenkins Should the plugin name be changed ?? Something without jenkins on it ?? Thank you, Andoni https://github.com/ChaitanyaChannella/BehaveResultsJenkinsPlugin -- 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/b6bd6430-eb12-43c3-a876-6a79d78a574b%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-dev/b6bd6430-eb12-43c3-a876-6a79d78a574b%40googlegroups.com?utm_medium=emailutm_source=footer . 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/CAMui946HT%2Bw_miBz_DmWqS9uX%3Dymo9WW4xO9iqm66sFH%2BizQVQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
inedo-buildmaster-plugin job config
The job for the inedo-buildmaster-plugin is a Maven job, but should be a Gradle job: https://jenkins.ci.cloudbees.com/job/plugins/job/gradle-jpi-plugin/ How can I get the changed over? Thanks Andrew -- 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/2757a8d1-85ab-4b11-b3ae-bc15d44b29dc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins Chat Room Plugin
+1 to just make those plugins without wiki page invisible in the update centre, because their origin and history are unknown. +1 to minimize plugins categories displayed in the update centre, because several plugins use too many categories (labels in the wiki) including one category for their own plugin (this could be edited directly in the wiki just I have just done for a few plugins). After this, the update centre needs more cleanup. Some plugins are displayed in double because of id changed after release, for example: - Wall display - MobileCloud - PaasLane - SMS Notifications And I suggest that some old and unmaintained plugins may need deprecation or at least a warning sign in the wiki: https://wiki.jenkins-ci.org/display/JENKINS/Proposed+Plugin+Deprecation - Emeric Le mardi 28 avril 2015 20:46:39 UTC+2, Baptiste Mathus a écrit : +1 to just make those plugins invisible until they fix those things. From my experience, the soft behaviour just does not work. Plugins developers will only fix their plugin if it prevents them from being publicly visible/usable. And users will still /suffer/ from this. The requirement we're talking is not much IMO. Or, maybe we could just require having some file inside the repository itself? 2015-04-28 20:36 GMT+02:00 Oleg Nenashev o.v.ne...@gmail.com javascript:: I would alter the UC's behavior in order to consider plugins as deprecated if there's no Wiki pages for them (probably with an extra whitelist based in jenkins-infra) with a minimal standardised set of sections (extra macros to poll poms?). BR, Oleg понедельник, 27 апреля 2015 г., 23:51:56 UTC+3 пользователь Daniel Beck написал: On 27.04.2015, at 13:36, Christopher Orr ch...@orr.me.uk wrote: It is possible to edit the ignores file in the update centre code [2], but that requires a pull request and getting somebody to merge it etc. They can easily be created within a minute or two on the Github UI, and I'd be happy to review and merge any such PR. (My open PR was mainly to allow community review, I could have committed it directly.) -- 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 javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-dev/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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/d2b682ad-fc0c-4ef4-9d23-ed58e4f4d1a1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins Chat Room Plugin
For example: what's this: https://twitter.com/jenkins_release/status/593756206839173120 +1 to just make those plugins invisible until they fix those things. From my experience, the soft behaviour just does not work. Plugins developers will only fix their plugin if it prevents them from being publicly visible/usable. And users will still /suffer/ from this. The requirement we're talking is not much IMO. Or, maybe we could just require having some file inside the repository itself? 2015-04-28 20:36 GMT+02:00 Oleg Nenashev o.v.nenas...@gmail.com: I would alter the UC's behavior in order to consider plugins as deprecated if there's no Wiki pages for them (probably with an extra whitelist based in jenkins-infra) with a minimal standardised set of sections (extra macros to poll poms?). BR, Oleg понедельник, 27 апреля 2015 г., 23:51:56 UTC+3 пользователь Daniel Beck написал: On 27.04.2015, at 13:36, Christopher Orr ch...@orr.me.uk wrote: It is possible to edit the ignores file in the update centre code [2], but that requires a pull request and getting somebody to merge it etc. They can easily be created within a minute or two on the Github UI, and I'd be happy to review and merge any such PR. (My open PR was mainly to allow community review, I could have committed it directly.) -- 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/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-dev/9eb9c587-e0b3-472c-a651-6d3d7ce1db64%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! -- 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/CANWgJS4xwReo3_pZgMugY4R1_H5TCuoQnftYn3nFRUQRJ5CdTQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Hosting Request for BuildMaster Plugin
Did I foget to send a reply? Here is the repository: https://github.com/jenkinsci/buildmaster-plugin https://github.com/jenkinsci/buildmaster-plugin Am 29.04.2015 um 12:19 schrieb Oleg Nenashev o.v.nenas...@gmail.com: +1 for publishing the plugin. Probably, buildmaster-plugin could be replaced to inedo-buildmaster[-cd]-plugin вторник, 28 апреля 2015 г., 3:04:18 UTC+3 пользователь andrew...@customs.govt.nz написал: Hi, I’d like to host a new Jenkins plugin at Jenkins-ci. The plugin will enable BuildMaster users (http://inedo.com/buildmaster http://inedo.com/buildmaster) to to request version information and trigger builds on a BuildMaster application as part of a Jenkins build process. GitHub plugin name: buildmaster-plugin Personal GitHub ID: andrew-sumner Existing GitHub repository: https://github.com/andrew-sumner/buildmaster-plugin https://github.com/andrew-sumner/buildmaster-plugin Regards Andrew Note: this is a duplicate as my last request never got any traction and I thought I'd try again... -- 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 mailto:jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/896ecb21-2eab-477e-9bbc-87b7243d798b%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-dev/896ecb21-2eab-477e-9bbc-87b7243d798b%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout 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/CF070B98-1CB9-4653-B787-2D52F23156F4%40gmail.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: Message signed with OpenPGP using GPGMail
