For a while back, Domi wrote the code [1] that tallies anonymized usage
statistics and parse them into JSON files. This is what drives the plugin
installation count stats in Wiki.
We noticed that some time ago, this started taking very long time to run
[2]. Whereas it used to take an hour or so, n
The problem still remains that the code in core needs to statically link to
stapler, so it is just not technically possible to move stapler into a
separate plugin.
2013/10/7 Domi
> Its not that I think it should not be shipped in the core, but it would
> make it easter to backport/fix stuff in
Its not that I think it should not be shipped in the core, but it would make it
easter to backport/fix stuff in older versions too.
Regards Domi
> Am 07.10.2013 um 22:12 schrieb Kohsuke Kawaguchi :
>
> Most of the things in core depends on it one way or another, so I don't think
> it's feasibl
Olivier, it's now at https://github.com/jenkinsci/maven-plugin
I was a also a bit surprised that it was moved without any prio
announcement - or question if it was cause issues for someone ...
cheers
Kutzi
Am 07.10.2013 22:04, schrieb Olivier Lamy:
What happened with the maven plugin?
Did I
Most of the things in core depends on it one way or another, so I don't
think it's feasible.
2013/10/7 Domi
> This might be a dummy question, but would it make sense to extract stapler
> into a separate plugin - like we do with other libs already? Is this even
> possible?
>
> Am 07.10.2013 um 1
What happened with the maven plugin?
Did I miss the announcement saying the scm location has changed?
Or an email asking if it will cause an issue to someone?
What is the technical (business?) reason to not ask?
Cheers
--
Olivier
--
You received this message because you are subscribed to the Goo
This might be a dummy question, but would it make sense to extract stapler into
a separate plugin - like we do with other libs already? Is this even possible?
> Am 07.10.2013 um 17:16 schrieb "Kevin Fleming (BLOOMBERG/ 731 LEXIN)"
> :
>
> Great! I'll experiment with it in a few weeks after a lo
Cool.
Let me look around there.
Thanks
--
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.
For more options, visi
Interesting. No denying what you propose would not be useful. But maybe at
least for Git you could consider using a post receive hook to lower the
load on your server and not have this kind of issue you're currently having.
My 2 cents.
Le 5 oct. 2013 17:10, "Sascha Vogt" a écrit :
> Hi,
>
> Yes,
Well, from my understanding there's actually already a bunch of post
actions that work this way. The first that comes to mind is the test result
publisher. It obviously can change the build status if tests are not
satisfying.
HTH
Le 4 oct. 2013 22:06, "Mike Caspar" a écrit :
> I am looking for s
:-(
About slave log spining, a ticket exist allready :
* https://issues.jenkins-ci.org/browse/JENKINS-19758
2013/10/7 Stephen Connolly
> nothing s coming to mind... but I'm in the middle of switching contexts to
> the feature that has the deadline!
>
>
> On 7 October 2013 15:42, Henri Gomez
Great! I'll experiment with it in a few weeks after a long overdue vacation :-)
- Original Message -
From: jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com
At: Oct 7 2013 11:12:13
@PostConstruct, @DataBoundSetter on fiels, and Descriptor.newInstance() all
fixed in 1.535
nothing s coming to mind... but I'm in the middle of switching contexts to
the feature that has the deadline!
On 7 October 2013 15:42, Henri Gomez wrote:
> Yep ;(
>
> I understand enterprise and deadline pretty well, I have the same on my
> side.
> About 5 second timeout enforced, it could by i
@PostConstruct, @DataBoundSetter on fiels, and Descriptor.newInstance() all
fixed in 1.535.
2013/10/5 domi
> Kohsuke,
> while you'r at it, there are more issues around this topic. e.g.
> Plugins still using newInstance() are not usable everywhere:
> https://issues.jenkins-ci.org/browse/JENKINS-
Yep ;(
I understand enterprise and deadline pretty well, I have the same on my
side.
About 5 second timeout enforced, it could by itself introduce issues and I
hope it will be configurable very soon.
Sadly all problems with SSH slaves bring us, CI team, in a very
unconfortable situation with our
On Sat, Oct 5, 2013 at 7:02 AM, Christoph Kutzinski wrote:
> [ERROR] Failed to execute goal
> com.cloudbees:maven-license-plugin:1.7:process (default) on project
> maven-plugin: The following dependencies are missing license information:
> [ERROR] javax.annotation:jsr250-api:1.0
Obviously this ca
On Sat, Oct 5, 2013 at 8:58 AM, Christoph Kutzinski wrote:
> As that is IMO is quite critical, can we have a release of the maven-plugin?
Go ahead.
> I'm not sure how this is handled now that the plugin is in it's own
> repository.
Same way as any other plugin. mvn release:prepare release:perf
At present it seems there is a 5 second timeout being enforced somewhere,
from reading those JIRA at least I'd like to spend some more time
investigating, but I have a new deadline looming for more enterprise
features to carve out!!! and I have to do some more stuff on literate, etc.
Hopefully
Hello,
You can find example here:
https://github.com/jenkinsci/cygwin-process-killer-plugin/blob/master/src/main/java/com/synopsys/arc/jenkinsci/plugins/cygwinprocesskiller/CygwinProcessKiller.java
On the slave:
- you can get channel to master via SlaveComputer.getChannelToMaster().
-
On Sat, Oct 5, 2013 at 9:03 PM, Tom Milligan wrote:
> The correct plugin artifactId is skytap-cloud-plugin.
Really the correct artifactId would be skytap-cloud. (Short names
should be include the words “Jenkins” or “plugin”.)
> Can you delete the entry for "skytap" in
> http://repo.jenkins-ci.o
On Sun, Oct 6, 2013 at 2:26 AM, Ikedam wrote:
> I think it can be done by modifying behaviors of EnvVars.
Be very careful here. From what I understand, the design is that an
EnvVars keeps track of whether it is supposed to be used on Unix
(case-sensitive) or Windows (case-insensitive), and these
>[Shameless plug]
>http://developer-blog.cloudbees.com/2013/10/ssh-slaves-reloaded.html
>[/Shameless plug]
Enterprise edition only isn't it ? ;(
> Anyway, in 1.3 vs 1.2 I didn't change the ssh connection logic, similarly
there is no changes outside of credentials since 0.27.
>We'd really need to
[Shameless plug]
http://developer-blog.cloudbees.com/2013/10/ssh-slaves-reloaded.html
[/Shameless plug]
Anyway, in 1.3 vs 1.2 I didn't change the ssh connection logic, similarly
there is no changes outside of credentials since 0.27.
We'd really need to know more about the ssh server that is being
You need to publish on your own. Just create a new release from the new
repository…
Ulli
Am 07.10.2013 um 13:21 schrieb Omer Shem-Tov :
> Thanks Ikedam for pushing it forward.
> Thanks Uli for forking the plugin. I'll get in touch with the author of
> matrix-reloaded plug-in.
> But As for my o
Thanks Ikedam for pushing it forward.
Thanks Uli for forking the plugin. I'll get in touch with the author of
matrix-reloaded plug-in.
But As for my opinion this plugin should be an integral part of Jenkins.
When you build a matrix you'll have an option to choose which combinations
you'll want to r
I created https://github.com/jenkinsci/matrix-combinations-plugin
Welcome aboard!
I still don't see, why both use cases should not be part of *one* plugin. Which
one, does not really matter. Can you please get in touch with the author of the
matrix-reloaded plug-in? At least you can share the
Am 06.10.2013 um 04:18 schrieb Ikedam :
> Hello, Ulli.
>
> You asked, and Omer responded.
> Why no further response from you?
>
I don't read every mail in this list, especially if the context is not clear.
> As Omer says, this plugin differs from Matrix Reloaded plugin even though
> their i
Hi Steven
With Jenkins 1.529 (slave 1.2, ssh creds 1.4), I had more and more often
failures between Jenkins and its SSH slaves:
"
FATAL: hudson.remoting.RequestAbortedException: java.io.IOException:
Unexpected termination of the channel
hudson.remoting.RequestAbortedException:
hudson.remoting.Req
Hi Jesse,
That solved the problem. - As soon as I added a "getResultsDir()" method to
the plugin class everything started working as expected. :^)
Thanks for your help.
On 4 October 2013 18:08, Jesse Glick wrote:
> On Fri, Oct 4, 2013 at 6:55 AM, RDR wrote:
> >
>
> Does your tool hav
29 matches
Mail list logo
