used in this CI job. Then it is necessary to fire again a new job that will build these packages. • If the merge is a clean fast-forward, then the packages that were built in this job would be valid, among different concurrent Conan instances. This is a typical scenario in CI servers, in which each job uses a different Conan package cache (defined by CONAN_USER_HOME environment variable). Every different Integration processes, it is recommended to have a different Conan package cache (CONAN_USER_HOME) for each job, in most of the cases, because the Conan package cache is not concurrent, and it might also have old

used in this CI job. Then it is necessary to fire again a new job that will build these packages. • If the merge is a clean fast-forward, then the packages that were built in this job would be valid, among different concurrent Conan instances. This is a typical scenario in CI servers, in which each job uses a different Conan package cache (defined by CONAN_USER_HOME environment variable). Every different Integration processes, it is recommended to have a different Conan package cache (CONAN_USER_HOME) for each job, in most of the cases, because the Conan package cache is not concurrent, and it might also have old

used in this CI job. Then it is necessary to fire again a new job that will build these packages. • If the merge is a clean fast-forward, then the packages that were built in this job would be valid, among different concurrent Conan instances. This is a typical scenario in CI servers, in which each job uses a different Conan package cache (defined by CONAN_USER_HOME environment variable). Every different Integration processes, it is recommended to have a different Conan package cache (CONAN_USER_HOME) for each job, in most of the cases, because the Conan package cache is not concurrent, and it might also have old

used in this CI job. Then it is necessary to fire again a new job that will build these packages. • If the merge is a clean fast-forward, then the packages that were built in this job would be valid, among different concurrent Conan instances. This is a typical scenario in CI servers, in which each job uses a different Conan package cache (defined by CONAN_USER_HOME environment variable). Every different Integration processes, it is recommended to have a different Conan package cache (CONAN_USER_HOME) for each job, in most of the cases, because the Conan package cache is not concurrent, and it might also have old

used in this CI job. Then it is necessary to fire again a new job that will build these packages. • If the merge is a clean fast-forward, then the packages that were built in this job would be valid, among different concurrent Conan instances. This is a typical scenario in CI servers, in which each job uses a different Conan package cache (defined by CONAN_USER_HOME environment variable). Every different Integration processes, it is recommended to have a different Conan package cache (CONAN_USER_HOME) for each job, in most of the cases, because the Conan package cache is not concurrent, and it might also have old

used in this CI job. Then it is necessary to fire again a new job that will build these packages. • If the merge is a clean fast-forward, then the packages that were built in this job would be valid, among different concurrent Conan instances. This is a typical scenario in CI servers, in which each job uses a different Conan package cache (defined by CONAN_USER_HOME environment variable). Every different Integration processes, it is recommended to have a different Conan package cache (CONAN_USER_HOME) for each job, in most of the cases, because the Conan package cache is not concurrent, and it might also have old

used in this CI job. Then it is necessary to fire again a new job that will build these packages. • If the merge is a clean fast-forward, then the packages that were built in this job would be valid, among different concurrent Conan instances. This is a typical scenario in CI servers, in which each job uses a different Conan package cache (defined by CONAN_USER_HOME environment variable). Every different Integration processes, it is recommended to have a different Conan package cache (CONAN_USER_HOME) for each job, in most of the cases, because the Conan package cache is not concurrent, and it might also have old

used in this CI job. Then it is necessary to fire again a new job that will build these packages. • If the merge is a clean fast-forward, then the packages that were built in this job would be valid, among different concurrent Conan instances. This is a typical scenario in CI servers, in which each job uses a different Conan package cache (defined by CONAN_USER_HOME environment variable). Every different Integration processes, it is recommended to have a different Conan package cache (CONAN_USER_HOME) for each job, in most of the cases, because the Conan package cache is not concurrent, and it might also have old

used in this CI job. Then it is necessary to fire again a new job that will build these packages. • If the merge is a clean fast-forward, then the packages that were built in this job would be valid, among different concurrent Conan instances. This is a typical scenario in CI servers, in which each job uses a different Conan package cache (defined by CONAN_USER_HOME environment variable). Every different Integration processes, it is recommended to have a different Conan package cache (CONAN_USER_HOME) for each job, in most of the cases, because the Conan package cache is not concurrent, and it might also have old

used in this CI job. Then it is necessary to fire again a new job that will build these packages. • If the merge is a clean fast-forward, then the packages that were built in this job would be valid, among different concurrent Conan instances. This is a typical scenario in CI servers, in which each job uses a different Conan package cache (defined by CONAN_USER_HOME environment variable). Every different Integration processes, it is recommended to have a different Conan package cache (CONAN_USER_HOME) for each job, in most of the cases, because the Conan package cache is not concurrent, and it might also have old