conan-io / conan-io/docs

Lockfile CI documentation glosses over possible difficulties in atomic Artifactory copy of multiple packages

Open
#1,935 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
125
Forks
382
Avg merge
22h 39m
Merged PRs (30d)
21

Description

At the end of https://docs.conan.io/en/latest/versioning/lockfiles/ci.html it states:

> If the merge is a clean fast-forward, then the packages that were built in this job would be valid, and could be copied from the repository `conan-build` to the `conan-develop`.

How would such a 'copy' be accomplished for more than one package in an atomic way?

From what I understand from jFrog tech support, Artifactory's copy mechanism is not guaranteed to be atomic. Can you confirm?

Given that, how do you suggest we move packages from `conan-build` to `conan-develop` in a way that ensures developers don't accidentally grab an inconsistent view of the world?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.