Hi there,
Running Jenkins 1.496, I have this maven project that executes a script as a
post step (execute shell option and then calls a script from the workspace).
The radio button for the "Execute shell" step is on "Run only if build
succeeds" however the script gets executed when a build fails
If you're a git user, instead of increasing the numebr of threads, you might
consider revisiting your polling definition. I was polling git once a minute
from multiple jobs until I discovered the "Git polling must die" blog posting
from Kohsuke.
See
http://kohsuke.org/2011/12/01/polling-mu
Could you have configured your Jenkins server to expect Git in a certain path
(where it is on the master), and then have placed it on a different path on the
slave?
Could you have configured your Jenkins server to automatically install Git as a
tool but then have instead installed it yourself
IIRC, you need to use a Junit TestRunner to run the test, so that Junit's
test lifecycle is followed.
-- Dean
On 1/15/13 11:22 AM, "jserup" wrote:
>I am creating a FreeStyleProject using this test class:
>
>import org.jvnet.hudson.test.HudsonTestCase;
>import org.apache.commons.io.FileUtils;
Thanks. I added a new job that runs on the same slave, the output makes me
think the environment is OK, but I still get the same error.
(Note, Git is installed at C:\Git -- i tried the standard Program Files
also, but got the same effect and was worried it may be a space in the name
issue)
Here
I had a Jenkins server present this message today:
"There are more SCM polling activities scheduled than handled, so the
threads are not keeping up with the demands. Check if your polling is
hanging, and/or increase the number of threads if necessary."
How do I go about increasing the number of
I think your assessment is correct. The Jenkins slave on that computer cannot
find the git executable. The "error performing command --version" would have
been "git --version" if the git executable had been found.
One way to diagnose that condition is to create a Jenkins job which executes on
Hi folks,
I use post build tasks to run some cleanup jobs, the problem is that post
build task is invoked after the current processes are aborted by Jenkins,
is there a plugin or workaround to run a script/command as part of post
build task before the process is actually aborted.
thanks,
Prave
I had a working jenkins build... then I started poking and am struggling to
get it back on its feet!
I *think* the error is that jenkins can not find the git path. It is in
the environment %PATH%
>From cmd, when I run:
C:\Users\ryan>git --version
git version 1.8.0.msysgit.0
The build error I
I am creating a FreeStyleProject using this test class:
import org.jvnet.hudson.test.HudsonTestCase;
import org.apache.commons.io.FileUtils;
import hudson.model.*;
import hudson.tasks.Shell;
public class AppTest extends HudsonTestCase
{
public void test1() throws Exception {
F
Hi All
We have multiple jobs chained together to form a single run.
We like to have an aggregated Recent Changes from previous jobs shown
in the last job Recent Changes section.
How do we accomplish that ?
Thanks
Hi everyone,
I'm desperately trying to get LDAP group based authentication to run. LDAP
user based security does work, but I can't get the groups to work. Most
obvious symptom is the "no entry"-Sign in front of every group.
I've debugged my installation using ldapsearch with those parameters:
ld
Hi,
If you use the Build step / Builder
"Trigger/call builds on other projects"
and check the checkbox
"Block until the triggered project finish their builds",
then the "parent" build will wait for the "child" to finish, and process
it's exit status as instructed by the three drop-down lists.
Hop
13 matches
Mail list logo