Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Job cloning doesn't clone tasks

Created: 12 Feb 2013 | 10 comments
SamTarr's picture
6 Agree
0 Disagree
+6 6 Votes
Login to vote

When cloning a job normally I don't want the tasks cloned. I would like it to create a new job with all the same tasks. If I have an image job that has 15 tasks and I build a new image I'd be much easier to clone the exisiting image job, remove the task that lays down the image and add a new one with my new image. As it works now it will clone all the tasks so I'll have several copies of each. This makes organization a nightmare. It also makes it difficult if I have to update one of the tasks in my image job. I'd have to update the each of the tasks that do the same thing instead of just updating one. 

Adding a checkbox to clone tasks after selecing the clone option would fix the problem. 

Comments 10 CommentsJump to latest comment

jlawson's picture

I would recommend changing the title of this to:
Job cloning should not clone tasks

but AMEN to this request.

0
Login to vote
resendesw's picture

I would also like to see this resolved.  I have no idea what the thought process was in cloning the tasks when a job was cloned.

0
Login to vote
Alex Bizjajev's picture

Hi,

The main idea was to allow user to change the tasks' settings in the cloned job without the affect on the initial job.

But I suppose this is a good suggestion to have an option to skip the creation of new copies of tasks while cloning a job. I have added this as a suggestion for the Task Server (although I cannot guaranty this will be implemented or provide any time-line).

Thank you,

Alex.

0
Login to vote
jlawson's picture

I think it should skip the cloning of the task by default but have an option to clone task also if checked.  It is very rare anyone is going to want to clone the task in a Job.  I can see where it might be a wanted option but in 99% of most cases I think users would rather clone a job and not the task then if there was one task they needed to modify they could go to that task and clone it only.

0
Login to vote
BugTastic's picture

If this is not implemented it would suggest that the guys who develop it dont know how its used on a day to day basis. Right from the first day i thought this was odd. Its a no brainer as they say.

Joe.

0
Login to vote
sgosden's picture

I agree it is annoying, but i found if you structure your jobs it is rarely needed. 

For imaging i always create a pre-image job and post image job (made up of multiple tasks) as these are always the same.I then have specific image task (which can be cloned and changed for specific images) and then jobs for core applications and jobs for custom applications.

So the image job is always the same with the exception of the specific image task and any specific custom jobs at the end. The image job then takes 2 minutes to create as it will just be made up of three jobs and the image task.

This also makes it very simple to update e.g. if you have lots of cloned image tasks and need to make a change to a pre image task you would have to make it on all of them. By using a pre-image job you can change a single task and it updates all the image jobs immediately.

I hope i explained this correctly, but i find this actually makes it very simple to use and manage and i only clone specific tasks.

 

 

 

0
Login to vote
BugTastic's picture

I gave up having jobs within jobs as it caused no end of problems. I'm on version 7 though so hopefully better in the later version which I'm in the process of implementing.

Joe.

 

0
Login to vote
jlawson's picture

I understand what you have done to mitigate the issue but it is still an issue - you still clone task.  This is what this idea is for is to have the option to choose to not clone or choose to clone.

Everyone discusses deployment jobs here as being the issue but I have many other jobs where this is a serious issue that are not deployment related.  It is just another thing that makes cleanup a big issue or I have to recreate the job to prevent the cleanup and add everything manually.

0
Login to vote
sgosden's picture

I have only really done jobs within jobs with 7.1. This has worked pretty well and i have configured this as many sites in this manor and they are working well

0
Login to vote
jellsworth's picture

Totally agree.  Thumb this up.

0
Login to vote