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
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
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
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:
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.
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/
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
+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
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
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
10 matches
Mail list logo
