script to delete jobs

rtan · Post by **rtan** » Tue Jun 27, 2006 10:34 pm

Hi,

I want to write a script that, among other things, deletes a number of jobs from a project. Is this possible?

ta.

chulett · Post by **chulett** » Tue Jun 27, 2006 11:18 pm

There is no command line mechanism to delete jobs. Curiousity forces me to ask - why do you think you need to do something like this?

ray.wurlod · Post by **ray.wurlod** » Wed Jun 28, 2006 1:05 am

Yeah, why? I can't think of any reason for wanting to do that. The number of keystrokes required to create the script is probably more than the number of mouse clicks required to delete the jobs using the GUI.

chulett · Post by **chulett** » Wed Jun 28, 2006 6:03 am

Perhaps it depends on what the 'among other things' things are?

kumar_s · Post by **kumar_s** » Wed Jun 28, 2006 6:14 am

Is by any chance, that you guys have decided not to give solutions with DS internal files.

chulett · Post by **chulett** » Wed Jun 28, 2006 6:18 am

I for one feel that would be a Very Bad Idea and should not be the kind of advice we hand out here willy-nilly. More than likely, all that will result of it would be a corrupted repository.

ray.wurlod · Post by **ray.wurlod** » Wed Jun 28, 2006 3:48 pm

Let's await rtan's answer to the "why" question.

Sure it can be done by hacking the Repository tables (not sure yet how to do this via the Metadata Delivery Service in Hawk, though). But this is definitely a high risk "solution" in inexperienced hands. What if the wrong piece is accidentally deleted? Do you force an export beforehand so that pieces can be recovered? Already you're taking more time than using the GUI client to delete jobs.

Further, using the GUI client means that DS_AUDIT is updated, so that there's a record of by whom and when the object was deleted. Would that capability need to be included in the script?

kduke · Post by **kduke** » Wed Jun 28, 2006 5:42 pm

I agree with Ray but this has been posted already.

rtan · Post by **rtan** » Wed Jun 28, 2006 7:16 pm

Hi all,
i'd like to automate the process of deleting an existing build and importing a full build. At the moment, I have a batch script which extracts a full build from VSS and imports it into DSManager. However, before this happens I have to manually delete the jobs/folders from manager. So to answer the 'why' question - it's purely to have an automated process for build migration.
thanks

kcbland · Post by **kcbland** » Wed Jun 28, 2006 7:25 pm

Why not version builds at a project level? For every major build, start a new project. For minor patch migrations, just overlay.

sud · Post by **sud** » Wed Jun 28, 2006 7:26 pm

rtan wrote:Hi all,
i'd like to automate the process of deleting an existing build and importing a full build. At the moment, I have a batch script which extracts a full build from VSS and imports it into DSManager. However, before this happens I have to manually delete the jobs/folders from manager. So to answer the 'why' question - it's purely to have an automated process for build migration.
thanks

But simply importing through your script will overwrite everything which should suit your purpose. If you are talking about removing all the instances of each job you just need to force compile all jobs.

ray.wurlod · Post by **ray.wurlod** » Wed Jun 28, 2006 8:27 pm

Beat me to it!! All you need to do then is delete those few jobs, if any, that are not in the new build. You will be able to generate a list of these from VSS.

I continue to recommend a manual process, or hire an expert (who is cognizant of the dangers) to create your script. Your support provider will be able to source one, IBM can provide these services, some of the posters here can also do so.

Peace · Post by **Peace** » Thu Jun 29, 2006 3:14 am

May I know what is VSS???

ray.wurlod wrote:Beat me to it!! All you need to do then is delete those few jobs, if any, that are not in the new build. You will be able to generate a list of these from VSS.

I continue to recommend a manual ...

kduke · Post by **kduke** » Thu Jun 29, 2006 5:53 am

Visual Source Safe.

sud · Post by **sud** » Fri Jun 30, 2006 1:27 pm

ray.wurlod wrote:

I continue to recommend a manual process, or hire an expert (who is cognizant of the dangers) to create your script. Your support provider will be able to source one, IBM can provide these services, some of the posters here can also do so.

And so they won't discuss the steps to do it. Cuz u kn, u gotta burn ur fingers to learn this stuff. For the bravehearts, I will urge em to use the long weekend

Take a backup and then do ur evil stuff and when u r convinced that u have blown up everything ... revert.

Provided u r a sudoer on the box ofcourse.
If you are caught in the act ... voila, ur fingers will be intact. Ur a** will be in line of course.