The VM where Jenkins CI is running, was reaching to a point of disk
space being full. Our Admin decided to increase the disk space. After
that the builds stopped working. Both "Build Now" link as well as
scheduled builds do not work anymore. Here is the exception details in
the log -
Failed to
The following groovy runs nice and quick on the master, but on my slave it
takes 6-7 minutes!!
def proc = "ssh -T g...@github.com".execute()
def b = new StringBuffer()
proc.consumeProcessErrorStream(b)
println proc.text
println b.toString()
Any help would be much appreciated!!
My company is auditing Jenkins as a build system, and our use case
requires us to run long builds (12 hours) on slave machines. Because a
persistent network connection must be maintained with the slave
machine during this whole duration, sometimes our builds fail because
of network hiccups. This ca
I have a job that listens to 5 git repos,
The job can be triggered if any of these repos had new changes committed via
git. (sometimes it's more than one repo).
(i will put each git repo in a different subdir to not mix them together.)
so what i want to do is this:
1. If a certain git repo had
Is anyone aware of a workaround for the Maven crash on Jenkin's build in OS
X that causes:
<===[JENKINS REMOTING CAPACITY]===>channel started
ERROR: Maven JVM terminated unexpectedly with exit code 134
In the one blog post I can find about it,
http://samuraism.jp/blog/2010/12/16/hudson_build_f
Anyone have any insights on getting parameters to work with the
notification plugin?
On Apr 25, 12:18 pm, giuliano wrote:
> I’m using thenotificationplugin. Mostly works great. Except that I’m
> getting no job parameters. And my job does have parameters. Any
> thoughts on why not and what I can d
Anyone can post an example of configuration with "Parameterized publishing"
enabled?
Thanks!
Hi,
I had a slave agent installed on RHEL 5.5 that communicates with
Jenkins ver. 1.413, it ran smoothly with JDK1.6.0_25, then i needed
JDK 1.7.0_04-b20 in the local machine running slave agent and my
problemas began. When i started the slave agent with the JDK1.7 i got:
Caused by: java.lang.Out
Hi,
I wasn't planning on executing the scripts, just scan them looking for
potential issues.
Here are a few tools that I've found:
checkbashisms, loker, shanal
I've integrated checkbashisms into Jenkins using the excellent
warnings plugin.
It certainly found some issues.
Has anyone tried loker,
