The is issue https://issues.jenkins-ci.org/browse/JENKINS-12905 "PATH variable
is not injected", but that was fixed in EnvInject 1.30.
> -Original Message-
> From: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jim
> McCaskey
> Sent: 28 June 201
Hello,
Is there some way to determine from a shell build step whether the current
job was scheduled or started manually (via web interface)? I'm trying to
implement a single job but i need slightly different behavior when
scheduling the job vs running it directly. If there isn't that's okay i
Hi,
I want to configure a job to start several jobs after one another. I only
found ways to start several jobs them at once not.
Does anyone know a solution for that
Thanks
Torsten
Hello,
I have a job that uses Powershell to exec one of the build's build steps.
The job can run, without problem, on either of two Windows XP slaves.
If I attempt to run the job on a Windows 7 slave, I get the following error:
"File C:\Users\lx00057\AppData\Local\Temp\hudson9076101655905735463.
with https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin
Am Freitag, 29. Juni 2012 11:28:26 UTC+2 schrieb Torsten Zander:
>
> Hi,
>
> I want to configure a job to start several jobs after one another. I only
> found ways to start several jobs them at once not.
> Does anyone know a solutio
You can’t just chain the jobs?
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Torsten Zander
Sent: Friday, June 29, 2012 5:28 AM
To: jenkinsci-users@googlegroups.com
Subject: Start one job after another
Hi,
I want to configure a job to start severa
I am unable to perform a git clone using a Jenkins instance for which I
have no root access. The symptom at this point is that the Git plugin is
running the clone command with an empty or NULL 'git' exe.
Here's some more details. I started out by enabling the Git plugin on the
assumption that
I'd like to be able to automatically display the current job's page whilst
the build is traversing a sequence of jobs.
I have added some user instructions to the Description fields of some later
jobs.
On Thursday, June 28, 2012 3:23:13 PM UTC+1, SeboPL wrote:
>
> Hi,
> I've got an idea and would
Check the BUILD_CAUSE environment variable value from your program.
By default, the values can be:
- MANUALTRIGGER
- SCMTRIGGER
- MANUALTRIGGER
UPSTREAMTRIGGER
Then, plugins (such as XTrigger plugins) can provide additional cause
values.
On Fri, Jun 29, 2012 at 10:19 AM, benjamin.a.lau
wrote:
>
Did you install to the home of the user running Jenkins?
Sent from my Windows Phone
--
From: Kurt Granroth
Sent: 6/29/2012 10:44 AM
To: jenkinsci-users@googlegroups.com
Subject: Git clone fails with NPE and 'missing' exe
I am unable to perform a git clone using a Jenki
Yes. $HOME==/home/jenkins, which is the directory specified as the Home
directory in Jenkins Config as well as the home for the user Jenkins is
running under.
On Friday, June 29, 2012 10:23:10 AM UTC-7, slide wrote:
>
> Did you install to the home of the user running Jenkins?
>
> Sent from my W
Hi All,
I have one job where I need to check out three separate git repos before
the job commences.
The git plugin lets you enter multiple repositories to clone from, but
looking in the workspace for the job, it appears that only the last one
in the list is actually checked out.
What am I
I have a parameterized job that has a number of dependencies that it copies
in using parametrized copy artifacts build steps, e.g.: copy:
sim-common-linux64/SIM_COMMON_REV=${SIM_COMMON_REV}.
If there isn't a build of sim-common-linux64 that matches the
SIM_COMMON_REV, that step fails, as you wo
Are you on a 64bit version of Windows, and if so, did you set the policy using
both the 32-bit and 64-bit PowerShell exe ? We had a similar error in the past
because the policy had been manually set from a command line, which used the
64bit exe, but Jenkins was using the 32bit PowerShell.
32-bi
Hello all,
I have another mystery after my upgrade for Jenkins 1.461 to 1.472. I have a
Maven project build that produces a very large .tar.gz. I get an error like
listed below when the build runs. Now I know it looks like a problem with
Maven, But when I run this manually it works. I'm als
Issue #12513 describes the
problem: https://issues.jenkins-ci.org/browse/JENKINS-12513
Apparently it's assigned so let's hope it gets solved in upcoming releases
of the plugin.
Gregory
Ding! Ding! Ding! Ding! That's it Chris!
That's the solution. I needed to Set-ExecutionPolicy for the 64bit
Powershell. I had only modified the 32bit version.
Thank you very much!
Hello all,
No need to answer this. I was finally able to reproduce the problem outside of
Jenkins.
-Jim
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jim McCaskey
Sent: Friday, June 29, 2012 3:04 PM
To: 'jenkinsci-us
There is also the conditional build step plugin which you can use which
will allow check the build cause and then run a single or multiple
buildstep(s).
https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin
You will need to have separate buildsteps in this case, for each of
You could try looking at the Multiple SCM plugin
https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+Plugin
I haven't used it myself, but it seems to allow you to do what you want.
Chris
On Friday, June 29, 2012 6:03:35 PM UTC+1, Chris Withers wrote:
>
> Hi All,
>
> I have one job wher
20 matches
Mail list logo