Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353516

Summary: Cleanup Signing Directories
Product: Community Reporter: Jesse McConnell <jesse.mcconnell>
Component: CI-JenkinsAssignee: Eclipse Webmaster <webmaster>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Jesse McConnell CLA 2011-08-01 13:25:40 EDT
for want of a better place, I'll file this here

When I wrote the maven signing plugin I left in some bits on the signing process so I could better debug what was going on.  Now that more people are using it I fixed an issue where these signed build were lingering around.  Once people update to this new version of the plugin the issue will go away but I wanted to flag the powers that be that you might want to go through and wipe out these accumulated signed builds.

if you look under a project like egit in the signer directory you'll see a UUID, under this UUID is the signed and unsigned project.  In the plugin now I just smoke this UUID directory itself after I have copied the good stuff out of it.

So I am not sure how you want to make smoking these old entries and anything that shows up before people migrate to the new version of the plugin.

perhaps anything over a day old that is under the signing directory that is a directory matching a UUID just delete it?

Anyway, heads up as this could save you some space on the build server.

cheers
Comment 1 Denis Roy CLA 2011-08-11 13:42:04 EDT
We already delete files older than 14 days in the signing area... But you've given me an idea for empty directories. I'll take care of this -- thanks for letting me know.