-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Windows 2008 R2
I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0.
On manual run is it:
H:\Jenkins
On automatical run is it:
H:\Jenkins\
In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one.
edit: Maybe I am wrong but maybe is it since Jenkins version 2.22 for all builds, and has nothing to do with manual triggering.
edit2: now I have 2.23 installed and found that a new created matrix job (previous was not a matrix job) was success first today and after a SCM change not
now the correct one:
for manual build:
HUDSON_HOME=H:\Jenkins
JENKINS_HOME=H:\Jenkins\
for automatic build:
HUDSON_HOME=H:\Jenkins
JENKINS_HOME=H:\Jenkins
my SCM trigger is tfs plugin version 3.2.0
[JENKINS-38130] JENKINS_HOME is set different on trigger manual build
Ronny Borchert
created issue -
Ronny Borchert
made changes -
| Description |
Original:
I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0. On manual run is it: H:\Jenkins On automatical run is it: H:\Jenkins\ In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one. |
New:
I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0. On manual run is it: H:\Jenkins On automatical run is it: H:\Jenkins\ In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one. edit: Maybe I am wrong but maybe is it since Jenkins version 2.22 for all builds, and has nothing to do with manual triggering. |
Ronny Borchert
made changes -
| Summary | Original: JENKINS_HOME is set different for manual build | New: JENKINS_HOME is set different during jenkins run |
Ronny Borchert
made changes -
| Description |
Original:
I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0. On manual run is it: H:\Jenkins On automatical run is it: H:\Jenkins\ In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one. edit: Maybe I am wrong but maybe is it since Jenkins version 2.22 for all builds, and has nothing to do with manual triggering. |
New:
I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0. On manual run is it: H:\Jenkins On automatical run is it: H:\Jenkins\ In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one. edit: Maybe I am wrong but maybe is it since Jenkins version 2.22 for all builds, and has nothing to do with manual triggering. edit2: now I have 2.23 installed and found that a new created matrix job (previous was not a matrix job) was success first today and after a SCM change |
Ronny Borchert
made changes -
| Summary | Original: JENKINS_HOME is set different during jenkins run | New: JENKINS_HOME is set different on trigger manual build |
Ronny Borchert
made changes -
| Description |
Original:
I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0. On manual run is it: H:\Jenkins On automatical run is it: H:\Jenkins\ In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one. edit: Maybe I am wrong but maybe is it since Jenkins version 2.22 for all builds, and has nothing to do with manual triggering. edit2: now I have 2.23 installed and found that a new created matrix job (previous was not a matrix job) was success first today and after a SCM change |
New:
I have installed Jenkins 2.20 and found today when I build a job manual that JENKINS_HOME is different as when it triggered by tfs plugin version 3.2.0. On manual run is it: H:\Jenkins On automatical run is it: H:\Jenkins\ In case it is a TFS plugin bug and is already fixed, I wanna only now what is the right one. edit: Maybe I am wrong but maybe is it since Jenkins version 2.22 for all builds, and has nothing to do with manual triggering. edit2: now I have 2.23 installed and found that a new created matrix job (previous was not a matrix job) was success first today and after a SCM change not now the correct one: for manual build: HUDSON_HOME=H:\Jenkins JENKINS_HOME=H:\Jenkins\ for automatic build: HUDSON_HOME=H:\Jenkins JENKINS_HOME=H:\Jenkins my SCM trigger is tfs plugin version 3.2.0 |
| Priority | Original: Blocker [ 1 ] | New: Minor [ 4 ] |
Ronny Borchert
added a comment - Yes it is. Yesterday there was an update of it, maybe solved it. | Component/s | New: envinject-plugin [ 15893 ] | |
| Component/s | Original: core [ 15593 ] |
is the envinject plugin installed?