Bug 491188 - [Cascading] copying a job with a cascading parent does not add new child reference to parent
Summary: [Cascading] copying a job with a cascading parent does not add new child refe...
Status: NEW
Alias: None
Product: Hudson
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Winston Prakash CLA
QA Contact: Geoff Waymark CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-06 16:09 EDT by Andrew McKeon CLA
Modified: 2016-04-06 16:09 EDT (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 Andrew McKeon CLA 2016-04-06 16:09:16 EDT 
When copying a job that has a cascading parent, that cascading parent should be updated with a new child reference to the new job. This is not happening resulting in mmissing "Cascading Children" references on the parent.

To reproduce create two jobs, where one job is the cascading parent of the other.
Verify that the parent lists the child job under "Cascading Children" and the child lists the parent under "Cascading Parent". Now copy the child job and save it. Verify that the child lists the parent under "Cascading Parent" but the parent does NOT have any reference to the new job under "Cascading Children"

Workaround: When copying a job with a cascading parent, on the configure page, set the Cascading job selection back to "None", wait for the refresh and then set the Cascading job selection back to the parent. This action seems to cause the parent to be updated as expected.

Tested on Hudson 3.3.3