Hmm... It actually appears twice:
<?xml version='1.0' encoding='UTF-8'?>
<build>
<actions>
...
<hudson.plugins.git.GitTagAction>
...
<ws>[full path to the workspace]</ws>
</hudson.plugins.git.GitTagAction>
</actions>
...
<workspace>[full path to the workspace]</workspace>
I suppose I'll keep a symbolic link from the old location to the new one
until all the jobs have run at least once.
Thanks!
On Thu, Nov 8, 2012 at 4:03 PM, Michaël Pailloncy <mpapo....@gmail.com>wrote:
> Each build keeps the workspace location in build.xml.
> I'm not sure if it's possible, but you could try to use a Groovy script
> with the Groovy console to iterate over all builds of all job and try to
> change this value with the new one.
>
> I hope this tip can help you.
>
> Michaël
>
>
> 2012/11/8 Xavier Nodet <xavier.no...@gmail.com>
>
>> Hello
>>
>> I would like to change the location of the workspace for some of the
>> agents in our Jenkins 1.456 installation.
>> Here's what I tried:
>> - disconnect the node
>> - let /old/FS/location be the configured FS path for the node
>> - mv /old/FS/location/workspace /new/FS/location
>> - change the configuration of the node such that the FS is now
>> '/new/FS/location'
>> - reconnect the node
>>
>> But when I then want to check the workspace for a job that is assigned to
>> the node, Jenkins tells me that there is no such workspace... So I have to
>> manually launch all the jobs...
>>
>> Is there a better way to do these changes?
>> Thanks.
>>
>> And I apologize for the 'Google Talk' spam earlier...
>>
>> --
>> Xavier Nodet
>>
>>
>
--
Xavier Nodet
