Artifacts sticking around

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

Artifacts sticking around

Rob Aldred
Hey! Happy new year all.
Artifacts that are generated by running tests on my project stick around even after they have been archived with the build.
So say the 1st time my build succeeds creates all the artifacts such as test outputs and logs
The second time it fails right at the start before any of the tests are run, hudson still has the previous artifacts in the workspace, so they get archived with the failed build.
should i just manually do some teardown by remove all the files build/artifacts or is there a build in way to stop this happening?

Thanks
--Rob


Reply | Threaded
Open this post in threaded view
|

Re: Artifacts sticking around

Sami Tikka
Hudson does not do any automatic clean-up for the job workspace, at
least for freestyle and matrix projects which are the only ones I have
experience on.

My build step is usually two commands:

make clean
make

The first command cleans the workspace of all generated files,
including artifacts.

-- Sami

2010/1/8 Rob Aldred <[hidden email]>:

> Hey! Happy new year all.
> Artifacts that are generated by running tests on my project stick around
> even after they have been archived with the build.
> So say the 1st time my build succeeds creates all the artifacts such as test
> outputs and logs
> The second time it fails right at the start before any of the tests are run,
> hudson still has the previous artifacts in the workspace, so they get
> archived with the failed build.
> should i just manually do some teardown by remove all the files
> build/artifacts or is there a build in way to stop this happening?
> Thanks
> --Rob
>
>

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

Reply | Threaded
Open this post in threaded view
|

Re: Artifacts sticking around

Rob Aldred
Sami, That's good to know, my project is a ruby app so I will do some clean up before I start.
Thanks

--Rob

2010/1/9 Sami Tikka <[hidden email]>
Hudson does not do any automatic clean-up for the job workspace, at
least for freestyle and matrix projects which are the only ones I have
experience on.

My build step is usually two commands:

make clean
make

The first command cleans the workspace of all generated files,
including artifacts.

-- Sami

2010/1/8 Rob Aldred <[hidden email]>:
> Hey! Happy new year all.
> Artifacts that are generated by running tests on my project stick around
> even after they have been archived with the build.
> So say the 1st time my build succeeds creates all the artifacts such as test
> outputs and logs
> The second time it fails right at the start before any of the tests are run,
> hudson still has the previous artifacts in the workspace, so they get
> archived with the failed build.
> should i just manually do some teardown by remove all the files
> build/artifacts or is there a build in way to stop this happening?
> Thanks
> --Rob
>
>

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


Reply | Threaded
Open this post in threaded view
|

Re: Artifacts sticking around

Mark Waite
In reply to this post by Sami Tikka
----- Original Message ----

> From: Sami Tikka <[hidden email]>
> To: [hidden email]
> Sent: Sat, January 9, 2010 2:32:58 PM
> Subject: Re: Artifacts sticking around
>
> Hudson does not do any automatic clean-up for the job workspace, at
> least for freestyle and matrix projects which are the only ones I have
> experience on.
>
> My build step is usually two commands:
>
> make clean
> make
>
> The first command cleans the workspace of all generated files,
> including artifacts.

The git plugin has a "clean" check box in its "Advanced" settings.  When checked, it uses the "git clean command to remove files from the workspace which are not known to git.  However, if you're not using git for source control, that check box won't help you.

Mark Waite


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

Reply | Threaded
Open this post in threaded view
|

Re: Artifacts sticking around

Rob Aldred
Mark,
I was looking for something like that as I am using git, i don't seem to have a clean option when configuring my build;
I'm using hudson 1.335 and git plugin 0.73

--Rob

2010/1/10 Mark Waite <[hidden email]>
----- Original Message ----

> From: Sami Tikka <[hidden email]>
> To: [hidden email]
> Sent: Sat, January 9, 2010 2:32:58 PM
> Subject: Re: Artifacts sticking around
>
> Hudson does not do any automatic clean-up for the job workspace, at
> least for freestyle and matrix projects which are the only ones I have
> experience on.
>
> My build step is usually two commands:
>
> make clean
> make
>
> The first command cleans the workspace of all generated files,
> including artifacts.

The git plugin has a "clean" check box in its "Advanced" settings.  When checked, it uses the "git clean command to remove files from the workspace which are not known to git.  However, if you're not using git for source control, that check box won't help you.

Mark Waite


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


Reply | Threaded
Open this post in threaded view
|

Re: Artifacts sticking around

Mark Waite
You'll want to upgrade to git plugin version 0.8.  It fixes the connection between Hudson and gitweb.  That makes the user experience much better when browsing changes from the Hudson "Recent Changes" and "Changes" links.

"Clean after checkout" was not available in 0.7.3, or at least it is not available on the 0.7.3 version I haven't yet upgraded on one machine.

The "Clean after checkout" is available under the lower "Advanced" button on the git section of the job configuration page.  As an example, for my job named "MarkWaite", the configure page at http://localhost:8080/job/MarkWaite/configure has a button "Advanced" in the end of the "Git" section.  Once "Advanced" is clicked, the "Clean after checkout" check box will be visible.

Mark

From: Rob Aldred <[hidden email]>
To: [hidden email]
Sent: Sun, January 10, 2010 9:22:45 AM
Subject: Re: Artifacts sticking around

Mark,
I was looking for something like that as I am using git, i don't seem to have a clean option when configuring my build;
I'm using hudson 1.335 and git plugin 0.73

--Rob

2010/1/10 Mark Waite <[hidden email]>
----- Original Message ----

> From: Sami Tikka <[hidden email]>
> To: [hidden email]
> Sent: Sat, January 9, 2010 2:32:58 PM
> Subject: Re: Artifacts sticking around
>
> Hudson does not do any automatic clean-up for the job workspace, at
> least for freestyle and matrix projects which are the only ones I have
> experience on.
>
> My build step is usually two commands:
>
> make clean
> make
>
> The first command cleans the workspace of all generated files,
> including artifacts.

The git plugin has a "clean" check box in its "Advanced" settings.  When checked, it uses the "git clean command to remove files from the workspace which are not known to git.  However, if you're not using git for source control, that check box won't help you.

Mark Waite


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


Reply | Threaded
Open this post in threaded view
|

Re: Artifacts sticking around

Rob Aldred
Got it, thanks Mark,
I never though to look for an update; i now have the option with 0.8
Does exactly what I needed it to do.
Thanks for you help

--Rob

2010/1/10 Mark Waite <[hidden email]>
You'll want to upgrade to git plugin version 0.8.  It fixes the connection between Hudson and gitweb.  That makes the user experience much better when browsing changes from the Hudson "Recent Changes" and "Changes" links.

"Clean after checkout" was not available in 0.7.3, or at least it is not available on the 0.7.3 version I haven't yet upgraded on one machine.

The "Clean after checkout" is available under the lower "Advanced" button on the git section of the job configuration page.  As an example, for my job named "MarkWaite", the configure page at http://localhost:8080/job/MarkWaite/configure has a button "Advanced" in the end of the "Git" section.  Once "Advanced" is clicked, the "Clean after checkout" check box will be visible.

Mark

From: Rob Aldred <[hidden email]>Sent: Sun, January 10, 2010 9:22:45 AM

Subject: Re: Artifacts sticking around

Mark,
I was looking for something like that as I am using git, i don't seem to have a clean option when configuring my build;
I'm using hudson 1.335 and git plugin 0.73

--Rob

2010/1/10 Mark Waite <[hidden email]>
----- Original Message ----

> From: Sami Tikka <[hidden email]>
> To: [hidden email]
> Sent: Sat, January 9, 2010 2:32:58 PM
> Subject: Re: Artifacts sticking around
>
> Hudson does not do any automatic clean-up for the job workspace, at
> least for freestyle and matrix projects which are the only ones I have
> experience on.
>
> My build step is usually two commands:
>
> make clean
> make
>
> The first command cleans the workspace of all generated files,
> including artifacts.

The git plugin has a "clean" check box in its "Advanced" settings.  When checked, it uses the "git clean command to remove files from the workspace which are not known to git.  However, if you're not using git for source control, that check box won't help you.

Mark Waite


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