Hi Eike and All,we (Obeo) had troubles to make our M4 contribution yesterday to the breaking of /shared/jobs no more accessible to hudson.
We made it working again by adding an extra step to our builds : (script shell)
# copy necessary files for promotion
rm -rf /shared/jobs/${JOB_NAME}/lastSuccessful
mkdir -pv /shared/jobs/${JOB_NAME}/lastSuccessful
cp -R PUT HERE ALL THE NECESSARY FILES FOR PROMOTION
/shared/jobs/${JOB_NAME}/lastSuccessful
and then I was able to use my promotion scripts as usual.so i re-created myself the exact same behavior has before, that is having access thru /shard/jobs to all the necessary files ( promotion script and artifacts to promote).
Denis, is this the good way to do ? like Eike, i don't understand the difference between this approach and before.
cheers and good luck for those being in trouble ;) Stéphane. Le 14/12/2011 07:08, Eike Stepper a écrit :
Am 07.12.2011 14:53, schrieb Denis Roy:On 12/07/2011 08:43 AM, Sven Efftinge wrote:On Dec 7, 2011, at 2:09 PM, Denis Roy wrote:So we *moved /shared/jobs* to a locally-mounted filesystem, which is *not shared*.So if this is the problem. Why can't you make it shared again?I don't understand. Is that a trick question? /shared/jobs was shared, and didn't work very well, so we've moved it.I may look dumb but I'm just not experienced in these things. But what exactly was the original problem? A) Hudson has/creates problems when accessing the jobs *through* NFS B) NFS has/creates problems when used on a folder locally mounted for Hudson? Cheers /Eike ---- http://www.esc-net.de http://thegordian.blogspot.com http://twitter.com/eikestepper _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
<<attachment: stephane_bouchet.vcf>>
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
