hudson:

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

hudson:

Tobias Neckel
Hello,

sorry in advance for a perhaps stupid question for which I searched the
maillist archive but found no response.

I have a lot of job couples for which the following situation holds:
Job A does svn checkout and builds a project on a tied slave. Job B
downloads (from the master) the executable generated in A to its
workspace on a tied slave and runs tests.

Obviously, hudson creates backups of the old executables (the name of
the executable is the same for each build number) and adds numbers to
these backups. Hence, my workspace grows linearly with the number of
builds (which are quite large).

Is there a way - besides manually triggering "wipe out workspace" in the
browser - to perform that action automatically? Via a checkbox in the
post build actions or sth. that I missed? Or via a script/separate job?

How do other groups solve this problem?

Thanks in advance
Tobias

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: hudson:

Em DauPhu
Hi,

I have an advanced option "Wipe out workspace" in the git (scm) configuration. The help shows:
=> Delete the contents of the workspace before building, ensuring a fully fresh workspace.

But unfortunately for you it looks like it's only in the git plugin. May be this plugin can help you:
http://wiki.hudson-ci.org/display/HUDSON/Hudson+Distributed+Workspace+Clean+plugin

On Wed, Jul 28, 2010 at 4:06 PM, Tobias Neckel <[hidden email]> wrote:
Hello,

sorry in advance for a perhaps stupid question for which I searched the maillist archive but found no response.

I have a lot of job couples for which the following situation holds:
Job A does svn checkout and builds a project on a tied slave. Job B downloads (from the master) the executable generated in A to its workspace on a tied slave and runs tests.

Obviously, hudson creates backups of the old executables (the name of the executable is the same for each build number) and adds numbers to these backups. Hence, my workspace grows linearly with the number of builds (which are quite large).

Is there a way - besides manually triggering "wipe out workspace" in the browser - to perform that action automatically? Via a checkbox in the post build actions or sth. that I missed? Or via a script/separate job?

How do other groups solve this problem?

Thanks in advance
Tobias

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: hudson:

Richard Bywater
Perhaps as an alternative you could also add a shell script to the
build steps to do the delete?

Richard.

On 7/29/10, Em DauPhu <[hidden email]> wrote:

> Hi,
>
> I have an advanced option "Wipe out workspace" in the git (scm)
> configuration. The help shows:
> => Delete the contents of the workspace before building, ensuring a fully
> fresh workspace.
>
> But unfortunately for you it looks like it's only in the git plugin. May be
> this plugin can help you:
> http://wiki.hudson-ci.org/display/HUDSON/Hudson+Distributed+Workspace+Clean+plugin
>
> On Wed, Jul 28, 2010 at 4:06 PM, Tobias Neckel <[hidden email]> wrote:
>
>> Hello,
>>
>> sorry in advance for a perhaps stupid question for which I searched the
>> maillist archive but found no response.
>>
>> I have a lot of job couples for which the following situation holds:
>> Job A does svn checkout and builds a project on a tied slave. Job B
>> downloads (from the master) the executable generated in A to its workspace
>> on a tied slave and runs tests.
>>
>> Obviously, hudson creates backups of the old executables (the name of the
>> executable is the same for each build number) and adds numbers to these
>> backups. Hence, my workspace grows linearly with the number of builds
>> (which
>> are quite large).
>>
>> Is there a way - besides manually triggering "wipe out workspace" in the
>> browser - to perform that action automatically? Via a checkbox in the post
>> build actions or sth. that I missed? Or via a script/separate job?
>>
>> How do other groups solve this problem?
>>
>> Thanks in advance
>> Tobias
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: hudson:

Alex Barna
Should this be done in the step 'make clean' or something similar ?

Alex.

2010/7/28 Richard Bywater <[hidden email]>:

> Perhaps as an alternative you could also add a shell script to the
> build steps to do the delete?
>
> Richard.
>
> On 7/29/10, Em DauPhu <[hidden email]> wrote:
>> Hi,
>>
>> I have an advanced option "Wipe out workspace" in the git (scm)
>> configuration. The help shows:
>> => Delete the contents of the workspace before building, ensuring a fully
>> fresh workspace.
>>
>> But unfortunately for you it looks like it's only in the git plugin. May be
>> this plugin can help you:
>> http://wiki.hudson-ci.org/display/HUDSON/Hudson+Distributed+Workspace+Clean+plugin
>>
>> On Wed, Jul 28, 2010 at 4:06 PM, Tobias Neckel <[hidden email]> wrote:
>>
>>> Hello,
>>>
>>> sorry in advance for a perhaps stupid question for which I searched the
>>> maillist archive but found no response.
>>>
>>> I have a lot of job couples for which the following situation holds:
>>> Job A does svn checkout and builds a project on a tied slave. Job B
>>> downloads (from the master) the executable generated in A to its workspace
>>> on a tied slave and runs tests.
>>>
>>> Obviously, hudson creates backups of the old executables (the name of the
>>> executable is the same for each build number) and adds numbers to these
>>> backups. Hence, my workspace grows linearly with the number of builds
>>> (which
>>> are quite large).
>>>
>>> Is there a way - besides manually triggering "wipe out workspace" in the
>>> browser - to perform that action automatically? Via a checkbox in the post
>>> build actions or sth. that I missed? Or via a script/separate job?
>>>
>>> How do other groups solve this problem?
>>>
>>> Thanks in advance
>>> Tobias
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: hudson:

Sami Tikka
You can clean up the workspace whenever and whereever it is most
convenient to you, in "make clean" or elsewhere, Hudson does not care.

I personally favor "make clean". But it depends. And it is a matter of opinion.

-- Sami

2010/7/29 Alex <[hidden email]>:

> Should this be done in the step 'make clean' or something similar ?
>
> Alex.
>
> 2010/7/28 Richard Bywater <[hidden email]>:
>> Perhaps as an alternative you could also add a shell script to the
>> build steps to do the delete?
>>
>> Richard.
>>
>> On 7/29/10, Em DauPhu <[hidden email]> wrote:
>>> Hi,
>>>
>>> I have an advanced option "Wipe out workspace" in the git (scm)
>>> configuration. The help shows:
>>> => Delete the contents of the workspace before building, ensuring a fully
>>> fresh workspace.
>>>
>>> But unfortunately for you it looks like it's only in the git plugin. May be
>>> this plugin can help you:
>>> http://wiki.hudson-ci.org/display/HUDSON/Hudson+Distributed+Workspace+Clean+plugin
>>>
>>> On Wed, Jul 28, 2010 at 4:06 PM, Tobias Neckel <[hidden email]> wrote:
>>>
>>>> Hello,
>>>>
>>>> sorry in advance for a perhaps stupid question for which I searched the
>>>> maillist archive but found no response.
>>>>
>>>> I have a lot of job couples for which the following situation holds:
>>>> Job A does svn checkout and builds a project on a tied slave. Job B
>>>> downloads (from the master) the executable generated in A to its workspace
>>>> on a tied slave and runs tests.
>>>>
>>>> Obviously, hudson creates backups of the old executables (the name of the
>>>> executable is the same for each build number) and adds numbers to these
>>>> backups. Hence, my workspace grows linearly with the number of builds
>>>> (which
>>>> are quite large).
>>>>
>>>> Is there a way - besides manually triggering "wipe out workspace" in the
>>>> browser - to perform that action automatically? Via a checkbox in the post
>>>> build actions or sth. that I missed? Or via a script/separate job?
>>>>
>>>> How do other groups solve this problem?
>>>>
>>>> Thanks in advance
>>>> Tobias
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]