[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] Hudson users: Please attach your builds to slaves
|
Matt you are correct. The slaves should be able to come and go as
necessary. thus why they don't share workspaces with the master. They
copy Archived artifacts back to the master.
Dave
On 09/24/2010 12:45 PM, Matthew Ward(Esq.) wrote:
Well part of it is due to the following post from the Hudson maintainer:
In In 1.236 I updated the error check so that it will warn people if
they
try to use a network mounted path, and improved the help HTML to call
out the fact that the path needs not visible to the master.
(http://hudson.361315.n4.nabble.com/Hudson-Slave-access-Remote-Dir-td369105.html)
As I understand it the slaves are supposed to 'manage'
themselves(workspace etc) and just return the results to the master.
-Matt.
The hudsonbuild user directory (which contains the workspace) is not
common/shared across all the nodes.
In talking with others, I do wonder if it should be. I'm not sure
why Matt set it up this way, but he's not in today, and I have made a
note to ask him.
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
