Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318451 - Please delete some hudsonbuild created files
Summary: Please delete some hudsonbuild created files
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: CI Admin Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-30 08:31 EDT by Paul Webster CLA
Modified: 2010-07-05 11:13 EDT (History)
2 users (show)

See Also:


Attachments
runIBuilde4 patch (1.12 KB, patch)
2010-06-30 11:20 EDT, Paul Webster CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Webster CLA 2010-06-30 08:31:07 EDT
As part of our build process, we run an e4 SDK build as e4Build.  Then we use hudson to create a 4.0 SDK build, and as part of that build it adds to a composite repo at /shared/eclipse/e4/build/e4/downloads/drops/4.0.0/targets/updates/4.0 which I can then sync onto download.eclipse.org.

The problem is I need to clean up some of the older child repos (just delete them) but because the subdirs were created by hudsonbuild:callisto-dev  I cannot delete them or even move them to another location.

I'm looking for a good suggestion on how to deal with this.  I can't have our hudson buildscript chown -R e4Build:user since chown says "no way".  Would the same restriction prevent e4Build from deleting those directories if hudson did a chmod -R a+w ? 

The userids I have to work with are pwebster (committer) and e4Build (local build-only id).

PW
Comment 1 Kim Moir CLA 2010-06-30 09:54:34 EDT
One suggestion I would have would be to 

1) Copy the entire composite repo to the build directory when you are mirroring
2) Add new child repos
3) Delete child repos as needed using the p2.composite.repository remove task
4) Rsync back with --delete to remove the files
Comment 2 Paul Webster CLA 2010-06-30 11:06:22 EDT
(In reply to comment #1)
> One suggestion I would have would be to 
> 
> 1) Copy the entire composite repo to the build directory when you are mirroring
> 2) Add new child repos
> 3) Delete child repos as needed using the p2.composite.repository remove task
> 4) Rsync back with --delete to remove the files

We do 1,2, and 4 now, by virtue of the fact that the hudson build creates the child repo in /shared/eclipse/e4/build/e4/downloads/drops/4.0.0/targets/updates/4.0

the problem is I don't  have permissions to clean it up, and hudson can't clean it up as part of a build because we need to say which ones we keep or remove (which would be do-able, but painful to update the scripts every time).

Do we put the 4.0 created update site back in the hudson workspace?  Then have my publish.sh script mirror it locally and manage an e4Build based composite repo?

PW
Comment 3 Paul Webster CLA 2010-06-30 11:20:20 EDT
Created attachment 173108 [details]
runIBuilde4 patch

put the update site back in hudson, and I'll modify my publish scripts to copy it out.

PW
Comment 4 Kim Moir CLA 2010-06-30 11:32:08 EDT
patch released and R4_HEAD builder tagged for next build
Comment 5 Paul Webster CLA 2010-07-05 08:53:21 EDT
OK, I've migrated my build to my e4Build userid to avoid permission problems.

Could one of the webmasters please get rid of the files in /shared/eclipse/e4/build/e4/downloads/drops/4.0.0/targets/updates/4.0-tmp for me?

build_done.txt          I20100623-1906  I20100627-1659  S-4.0RC0-201006181748
compositeArtifacts.jar  I20100624-1511  I20100628-2215
compositeContent.jar    I20100625-0821  I20100629-2126

I don't have permissions to remove most of them.

PW
Comment 6 Eclipse Webmaster CLA 2010-07-05 10:53:47 EDT
Done.

-M.
Comment 7 Paul Webster CLA 2010-07-05 11:13:37 EDT
Thanx, this issue is now complete.

PW