The attached will do some of that.  it updates a dummy bldeploy job w/ the deploy times and then applies that 'template' to the remediation options and then schedules the patching job to run.

can you run the deploy jobs immediately after analysis or you do you need to schedule them in the future ?  you should be able to do something like run the patching job + auto-remediation, call it again - and check the results until there are no missing patches.  there's a couple Unreleased blcli commands and documentation  that will let you get the count of servers w/ missing patches and also one in the utility namespace to dump out the results that you could text-process for the count.

i'll see if i can work up an example.

sorry about the delay - something like the below should work.  the patching job should already be setup for auto-remediation and the 'execute now' set in the deploy options in the patching job.

so it will run the job, generate remediation artifacts and deploy them, then check if there were servers missing patches.  if there were, it re-runs the job.  if no patches are missing then no remediation artifacts are generated, otherwise it keeps doing that.  i put a limit on how many times that loop happens.

blcli_setjvmoption -Dcom.bladelogic.cli.execute.quietmode.enabled=true

blcli_setoption serviceProfileName defaultProfile

blcli_setoption roleName BLAdmins

blcli_connect

patchingJob="/Workspace/Patching Jobs/WindowsPatchingJob"

#dummyDeployJob="/Workspace/DummyDeploy"

runAnalysis()

{

blcli_execute PatchingJob getDBKeyByGroupAndName "${patchingJob%/*}" "${patching                                                 Job##*/}"

blcli_storeenv jobKey

blcli_execute Job executeJobAndWait ${jobKey}

blcli_storeenv jobRunKey

}

getResults()

{

        missingServers=""

        missingCount=0

        blcli_execute JobRun jobRunKeyToJobRunId ${jobRunKey}

        blcli_storeenv patchingJobRunId

        blcli_execute JobRun findPatchingJobChildrenJobsByRunKey ${patchingJobRu                                                 nId}

        blcli_execute JobRun getJobRunId

        blcli_execute Utility setTargetObject

        blcli_execute Utility listPrint

        blcli_storeenv patchAnalysisJobRunIds

        for jobRunId in ${patchAnalysisJobRunIds}

                do

                blcli_execute JobRun findById ${jobRunId}

                blcli_execute JobRun getType

                blcli_storeenv jobRunType

                if [[ ${jobRunType} != 7033 ]]

                        then

                        blcli_execute PatchAnalysisResult findJobResultByAnalysi                                                 sJobRunId ${jobRunId}

                        blcli_execute JobResult getResultId

                        blcli_storeenv patchAnalysisJobResultId

                        blcli_execute PatchAnalysisResult findServersWithMissing                                                 Patches ${patchAnalysisJobResultId}

                        blcli_execute SDeviceHeader getName

                        blcli_execute Utility setTargetObject

                        blcli_execute Utility listPrint

                        blcli_storeenv missingServers

                        missingServers=(${missingServers})

                        missingCount=$((${missingCount}+${#missingServers[@]}))

                fi

        done

}

missingCount=1

i=0

while [[ ${missingCount} -gt 0 ]] && [[ ${i} -lt 5 ]]

        do

        let i+=1

        runAnalysis

        getResults

        echo "missingPatchCount: ${missingCount}"

        echo "i=${i}"

done

If the dummy job doesn’t override the options for the pre- and post- script location you can just set it directly in the deploy options in the patching job

I don’t believe you can set those options in the blcli.  once they are set in the gui they should stay set.  i thought all you were doing is running the analysis/auto-remediation, re-running analysis and looking for when there are no missing patches ?

yeah - the issue is that not all of the options are inherited from the dummy and you can't edit all the options in the template deploy job inside the patching job.

so what settings do you need to have set in the generated deploy?  just 'execute now' and the pre- post- path ?  any others ?

changing the pre/post install command will increment the dbkey of the template deploy.  there's no way to update the remediation job and patching job w/ the new association.  similar thing w/ the execute now.