Is there a native way to have multiple versions of the same notebook/cluster/workflow?

[KiavData_78669]

Notebooks code, clusters and workflows definitions can evolve through time. When used in production, I would like to support old versions. Is there a way to run a job referring to a certain notebook version, using a given cluster version? Of course, I could encode the version within the resources names, but that's not the best approach.

[Debayan]

Hi, Could you please confirm if you are talking about this version: https://docs.databricks.com/notebooks/notebooks-code.html#version-history

[KiavData_78669]

Let's say I have a job that runs a notebook version '1' on cluster version 'a'. Then, I make changes to the notebook and the cluster, having therefore the version '2' for the notebook and version 'b' for the cluster. I want to be able to execute the job with notebook '1' and cluster 'a' as before and also the job with notebook '2' and cluster 'b'. Is this supported by databricks? It may be done using that versioning system that you're referring to, the problem is that I'm willing to understand if this is feasible

[Anonymous]

Hi @Kiavi Data​ 

Thank you for posting your question in our community! We are happy to assist you.

To help us provide you with the most accurate information, could you please take a moment to review the responses and select the one that best answers your question?

This will also help other community members who may have similar questions in the future. Thank you for your participation and let us know if you need any further assistance!