goto labels not found in duplicate job queue

[suew]

I have a job queue that does several steps in order to deploy a custom application. Some of the steps include custom deployment objects that include a version number. I wanted to replicate the same queue for a new version. Rather than creating a new queue, which is somewhat tedious for lots of steps, I exported the existing items and edited the txt (xml) file. I copied the queue and versioned deployment objects, renaming them and replacing the version number with my new version. Nothing else was changed. I then imported these new items. The objects work fine, but the queue branching doesn’t work. Each time a goto is attempted, it fails with errors such as “Job Queue: Execution continuing. Label:Uninstall does not exist.” These labels do exist.

I then created another job queue from scratch in Batch Patch with the same labels, same deployment objects, same steps. This queue works fine.

Is there some hidden something about labels that makes duplicating them in the xml fail? We’ll need to periodically update for new versions while maintaining old ones, and it would be a lot easier to do a quick find and replace for a version number in a file.

Thanks

[doug]

My guess is that probably when you modified the XML directly the issue was created due to line breaks or spaces. Either you accidentally created a space or line break without realizing, or your text editor uses a different line break format than what BatchPatch is anticipating, causing things to appear correct to you as the viewer, but in the actual data of the text file it’s coded differently (for example ‘\n’ vs ‘\r\n’).

I would suggest that instead of creating a brand new job queue from scratch, you simply use your existing job queue as a template for the new queue. So if you go into the job queue window and load your saved queue by double-clicking the saved queue in the list of saved queues (or by clicking the double-left-arrow), you can then give it a new title, and you can replace just the specific steps/lines that you care to replace. Then save it. This way the old queue will still be there, and now the new queue will also exist. This should be quicker than exporting to XML, modifying, importing. And it will also ensure that things work properly in the new queue.

[Author]

Posts