Archiving build environment

[MartinZ]

We started a new project using nRF Connect SDK & Zephyr. Installation of development tools is very easy and convenient using VSC add-ons. However, we are concerned about the long-term project maintainability. Namely, we would like to be able to rebuild the project with all NCS dependencies and obtain the same binary after some time when the versions of NCS, VSC plugins or even VCS we are currently using might not be available any more.

So we would like to archive the whole tool suite needed to build the project together with our code. Do you have a ready-made scenario on how to do this effectively, i.e. which folders to back up to be able to easily reestablish the environment on another PC without downloading anything from the internet?

[runsiv]

Hi Martin

I have asked internally to hear if there is any recommendation. My suggestion would be to either create a VM or maybe a docker image which contains everything you need for the project. 
I will update when I get internal feedback

Regards

Runar

[runsiv]

Update: 

VSCode isn't required to build,   

Git is required  (youcan archive the repos somewhere else if they don't trust GitHub) 

 

Every tool version is specified for every commit with these 2 files: 

  - https://github.com/nrfconnect/sdk-nrf/blob/main/scripts/requirements-fixed.txt

  - https://github.com/nrfconnect/sdk-nrf/blob/main/scripts/tools-versions-linux.yml  

 

Nordic provide a 'bundle' with these files for download as a zip for every tag:

 https://files.nordicsemi.com/ui/api/v1/download/contentBrowsing/NCS/external/bundles/v3/index-linux-x86_64.json?isNativeBrowsing=true

and this bundle wrapped in a container: 

https://github.com/nrfconnect/sdk-nrf/pkgs/container/sdk-nrf-toolchain