How to preserve job run history when deploying with DABs

[mkEngineer]

Hi

I’m having an issue when deploying jobs with DABs. Each time I deploy changes, the existing job gets overwritten,  the job name stays the same, but a new job ID is created. This causes the history of past runs to be lost.

Ideally, I’d like to update an existing job while keeping both the job name and the full run history. Has anyone found a best practice or configuration for handling this? Otherwise, I dont see the point of using DABs if history is lost for each? 

Thanks in advance!

[mkEngineer]

@Walter_C @Alberto_Umana 

[Coffee77]

You are not deploying DAB correctly. You MUST use same ID for your jobs. Assigning only same names will create new jobs. If needed, ping me back for further details. It is a very typical issue when starting with DAB 🙂

[Coffee77]

Yu must preserve content in green, that is a unique identifier for the Job basically. Property "name" acts as a kind of "alias" this case:

[Coffee77]

By the way, this is a typical exam question in Databricks certification exams 😎

[-werners-]

do you run bundle destroy perhaps?  because that will generate a new job id.

[Coffee77]

Despite using different keys but same names, original jobs should remain indeed unless destroying them