need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe using the locked versions for both libb/0.2@user/testing and liba/0.1@user/testing, as this was the snapshot of existing versions when the CI pipeline started, even if later a liba/0.2@user/testing was created

need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe using the locked versions for both libb/0.2@user/testing and liba/0.1@user/testing, as this was the snapshot of existing versions when the CI pipeline started, even if later a liba/0.2@user/testing was created

need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe using the locked versions for both libb/0.2@user/testing and liba/0.1@user/testing, as this was the snapshot of existing versions when the CI pipeline started, even if later a liba/0.2@user/testing was created

need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe using the locked versions for both libb/0.2@user/testing and liba/0.1@user/testing, as this was the snapshot of existing versions when the CI pipeline started, even if later a liba/0.2@user/testing was created

the use of only one version throughout the whole dependency graph. Lockfiles Lockfiles allow a snapshot of a dependency graph used for a build to be taken, and the build to be reproduced exactly at a need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe

the use of only one version throughout the whole dependency graph. Lockfiles Lockfiles allow a snapshot of a dependency graph used for a build to be taken, and the build to be reproduced exactly at a need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe

the use of only one version throughout the whole dependency graph. Lockfiles Lockfiles allow a snapshot of a dependency graph used for a build to be taken, and the build to be reproduced exactly at a need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe

the use of only one version throughout the whole dependency graph. Lockfiles Lockfiles allow a snapshot of a dependency graph used for a build to be taken, and the build to be reproduced exactly at a need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe

the use of only one version throughout the whole dependency graph. Lockfiles Lockfiles allow a snapshot of a dependency graph used for a build to be taken, and the build to be reproduced exactly at a need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe

the use of only one version throughout the whole dependency graph. Lockfiles Lockfiles allow a snapshot of a dependency graph used for a build to be taken, and the build to be reproduced exactly at a need to fetch the code from external origins when building from sources. It can be considered a “snapshot” of the source code. • Using the scm attribute of the conanfile to capture the remote and commit 1@user/testing Now we want to start developing and testing the code for pkgb, but we want to create a “snapshot” of the dependency graph, to isolate our development from possible changes (note that the recipe