Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 324383

Summary:	[new hudson] where is my workspace ?
Product:	Community	Reporter:	Bouchet Stéphane <sbouchet>
Component:	CI-Jenkins	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Bouchet Stéphane

2010-09-03 05:04:17 EDT

hi,

i am trying to get a sucessfull build for EEF using the new hudson instance.

i got two problems. 

first, the signing is gone again [1]

then the build continue and finishes in SUCCESS. but the archiving of artifacts fails because there is nothing in the workspace ? 

BUILD SUCCESSFUL
Total time: 70 minutes 51 seconds
Archiving artifacts
ERROR: No artifacts found that match the file pattern "build/?20*/**/**.*". Configuration error?
ERROR: 'build/?20*/**/**.*' doesn't match anything, but '**/**.*' does. Perhaps that's what you mean?
Sending e-mails to: goulwen.lefur@obeo.fr stephane.bouchet@obeo.fr
Finished: FAILURE

when i go to the workspace page [2], there is only the cvs contents that hudson gets, bu no trace of any builds directory that is used to build.

More creepy, all the build process is fine, using /opt/users/hudsonbuild/.hudson/jobs/emf-eef-integration/workspace/build/

the hudson workspace is badly mapped ??



[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=324170
[2] https://hudson.eclipse.org/hudson/job/emf-eef-integration/ws/

Comment 1 Eclipse Webmaster

2010-09-09 10:09:38 EDT

I think this is an artifact of how the slaves and master interact.  The slave creates its workspace in /opt/users/hudsonbuild/workspace when it runs jobs, but your job expects to write into /opt/users/hudsonbuild/.hudson/job/my_job/workspace so that is mounted on the slaves from the master(in the same location).  So when your build is finishing the slave is trying to 'clean' /opt/users/hudsonbuild/workspace/my_job instead of /opt/users/hudsonbuild/.hudson/job/my_job/workspace.

-M.

Comment 2 Bouchet Stéphane

2010-09-09 10:34:39 EDT

(In reply to comment #1)
> I think this is an artifact of how the slaves and master interact.  The slave
> creates its workspace in /opt/users/hudsonbuild/workspace when it runs jobs,
> but your job expects to write into
> /opt/users/hudsonbuild/.hudson/job/my_job/workspace so that is mounted on the
> slaves from the master(in the same location).  So when your build is finishing
> the slave is trying to 'clean' /opt/users/hudsonbuild/workspace/my_job instead
> of /opt/users/hudsonbuild/.hudson/job/my_job/workspace.
> 
> -M.

hummm, not sure i am clear about my problem :) 


the build is fine,the process finishes with a BUILD SUCESSFULL, but when hudson wants to archive the artifacts just being built, it looks on the /build folder in the job's workspace, and cannot find it. 

Manually, if i look at the same workspace place, i cannot find any "build" folder that must be there. 

i am using the hudson UI to look at the job's workspace, that is : 
https://hudson.eclipse.org/hudson/job/emf-eef-integration/ws/

it should be mapped to /opt/users/hudsonbuild/.hudson/jobs/emf-eef-integration/workspace , but i cannot ssh to hudson to see if it exact or not.

so, the build is making some stuff somewhere, but i don't know where exactly.

Comment 3 Eclipse Webmaster

2010-09-09 11:36:13 EDT

> it should be mapped to
> /opt/users/hudsonbuild/.hudson/jobs/emf-eef-integration/workspace 

This is only 'true' for builds run on the master instance.  Slaves use another path for their workspace, and since Hudson knows your job was run on a slave it's pointing you there.  But within your job you're using /opt/users/hudsonbuild/.hudson/jobs/emf-eef-integration/workspace and the slave can't 'see' into that workspace.

-M.

Comment 4 Bouchet Stéphane

2010-09-10 03:26:18 EDT

(In reply to comment #3)
> > it should be mapped to
> > /opt/users/hudsonbuild/.hudson/jobs/emf-eef-integration/workspace 
> 
> This is only 'true' for builds run on the master instance.  Slaves use another
> path for their workspace, and since Hudson knows your job was run on a slave
> it's pointing you there.  But within your job you're using
> /opt/users/hudsonbuild/.hudson/jobs/emf-eef-integration/workspace and the slave
> can't 'see' into that workspace.
> 
> -M.

ok, so until i use the cbi system, i must tide to master.. 

i'll try that.

Comment 5 Bouchet Stéphane

2011-02-24 07:49:35 EST

fixed.

My jobs are now correctly building.