Bug 423374 - Moving job from one team to another team leave directory with job with builds directory and _runmap.xml file
Summary: Moving job from one team to another team leave directory with job with builds...
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Core (show other bugs)
Version: 3.1.0   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-05 15:32 EST by Stuart Lorber CLA
Modified: 2013-12-05 20:22 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stuart Lorber CLA 2013-12-05 15:32:39 EST 
I moved a job from one team to another team.

The jobs moved however some artifacts are left over:

jobname/builds/_runmap.xml

This is not consistent.  Sometimes it leaves this file and sometimes it doesn't.

May be related to Bug #423356.
Comment 1 Bob Foster CLA 2013-12-05 17:48:29 EST 
It depends if there is a job/build in memory pointing to the old location that gets updated. Can you reproduce this in 3.1.1-RC1?
Comment 2 Stuart Lorber CLA 2013-12-05 19:45:06 EST 
I saw the problems with doing any of these type of operations when I was doing test runs of our migration.

This issue occurred when jobs were definitely not running and it was happening to about 1/2 to 2/3 of the jobs I moved.

Note that many of these jobs had many previous builds with many artifacts per build.

I would be happy to try this in a test environment with 3.1.1 RC1 of I can get the link.

Also, many of these jobs were migrated from my 2.2.1 system but I made sure proper permissions were on all artifacts (hudson:hudson) on CentOS.

Seemed to be the same behavior as the referenced ticket I put in about shelved jobs.
Comment 3 Stuart Lorber CLA 2013-12-05 20:22:16 EST 
My apologizes.

Per a previous email exchange about this issue a bug was created:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=422286

Note that I'm still having this problem but will try to produce in 3.1.1 (when I can get the link).

Thank you again.