Editing an Existing Job
When you edit an existing job, ePublisher AutoMap presents the windows used to create the job as tabs of the Edit Job window. Select the appropriate tab that contains the information you want to modify. Editing a composition job opens the Composition Job window instead, which is the same window you used to create it. For more information, see Creating a Composition Job.
To edit an existing job
Start ePublisher AutoMap.
Select the job to edit in the ePublisher AutoMap main window.
On the Job menu, click Edit.
Select the appropriate tab and modify the values as needed. For more information about a field, click Help.
Click OK.
Setting Build Options for a Job
The Job Info tab includes a Build options area that stores build behavior in the job file itself. Because the options travel with the job, they apply however the job runs — on its schedule, from Run, or from a direct command-line invocation.
Skip reports
Skips report generation for every target the job builds. Reports add time to a build, so skipping them shortens conversions on large jobs. This option is cleared by default.
Verbose logging
Controls how much the job records while it builds. This option is selected by default and preserves the full output. Clear it to omit the generation engine's step-by-step progress messages from the console and from the job log, leaving milestone, warning, and error messages — which reduces a scheduled job's log to what needs attention.
These options do not replace the equivalent command-line options; the two combine. Either the Skip reports option or the --skip-reports option skips reports. Either clearing Verbose logging or passing -q (--quiet) quiets the run, so a job that leaves the option selected can still be run quietly from a script.
Note: Clearing Verbose logging affects the job log only. The per-target
generate.logfile always keeps full detail for troubleshooting.
Defining Output Destinations Inside a Job
Output destinations are normally stored per Windows user on the computer that deploys, which means a job only deploys where a matching destination is defined. The Job Deploy Destinations tab lets a job carry destination definitions of its own, so the definition travels with the job — into version control, onto a build server, or into a scheduled task that runs as another Windows account.
Definitions on this tab belong to the job rather than to any one target. Once a destination is defined here, every target of the job can select it by name in the Deploy to list on the Target Configuration tab, and a new definition appears in that list as soon as you return to the tab. When the job runs, a destination defined in the job takes precedence over a destination of the same name defined on the computer, so pointing a job somewhere else stays a one-place change.
To define an output destination inside a job
Start ePublisher AutoMap.
Select the job to edit in the ePublisher AutoMap main window.
On the Job menu, click Edit.
Select the Job Deploy Destinations tab.
If you want to add a destination, click Add Folder... or Add Amazon S3..., complete the fields for that deployment type, and then click OK.
If you want to change a destination, select it in the list and click Edit.... You can also double-click the destination.
If you want to remove a destination, select it in the list and click Remove. Targets that still name the removed destination keep the name, so update them or define the name elsewhere before the job runs.
Click OK.
Note: Only Folder and Amazon S3 destinations can be defined inside a job, because neither stores a credential. Deployment types that hold a user name and password are not accepted in a job file; define those on the computer instead. For more information, see Defining Output Destinations.
On a build server you can supply the same definitions from a file rather than storing them in each job, using the --deploysettings option. A definition carried in the job still wins over one supplied that way. For more information, see CLI Syntax and Reference.