Recipe not promoted.

[klausholstjacobsen]

Conan 2.16.1
Latest extensions

I have two remotes "development" and integration".
My normal scenario is to produce a package, upload to development and then promote from development to integration with conan art:promote --url $ARTIFACTORY_SERVER_URL --from development --to integration package-list.json, where package list contain the new package.

This works perfectly under normal conditions.

But, If i do the above, and then remove the packages with

conan remove xxx/1.2.3 -r development
conan remove xxx/1.2.3 -r integration
conan remove xxx/1.2.3

followed by a rebuild and new promote i see this feedback from the promote call:

-------- Promoting _/xxx/1.2.3/_/d3b2bb6d3d3425c4e46e19d7f2cb8d7a0ac4df9d/export/ --------
WARN: Destination already exists, skipping
-------- Promoting _/xxx/1.2.3/_/d3b2bb6d3d3425c4e46e19d7f2cb8d7a0ac4df9d/package/0338223f030306698e87a28cfdb373ae1a58e02a/3afa9e57f0f9a16cf4a2b59beb400ae2 --------
Promoted file
-------- Promoting _/xxx/1.2.3/_/d3b2bb6d3d3425c4e46e19d7f2cb8d7a0ac4df9d/package/37be195f18e1b378d8ca47f669582c3c4288686c/954a6fde29f6fcac11ea28ff4a744e13 --------
Promoted file

And yes, the "export" folder containing the recipe has not been promoted:
"development" repo:

"integration" repo:

Subsequent conan list... also tell me that the recipe exists in "development" but not in "integration"!

Is this and error or am I doing something wrong?

[AbrilRBS]

Hi @klausholstjacobsen thanks for the report. What version of Artifactory are you using? Very old versions had a bug regarding package deletions that you might be triggering, but otherwise I'm trying to reproduce this locally,and so far I've not been able to.

My steps:

$ conan upload "zlib/1.3.1#b8bc2603263cf7eccbd6e17e66b0ed76:dbb40f41e6e9a5c4a9a1fd8d9e6ccf6d92676c92" -r=dev -f=json > pkglist.json

======== Uploading to remote dev ========

-------- Checking server for existing packages --------
zlib/1.3.1: Checking which revisions exist in the remote server
Connecting to remote 'dev' with user 'abril'

-------- Preparing artifacts for upload --------

-------- Uploading artifacts --------
zlib/1.3.1: Uploading recipe 'zlib/1.3.1#b8bc2603263cf7eccbd6e17e66b0ed76' (6.4KB)
zlib/1.3.1: Uploading package 'zlib/1.3.1#b8bc2603263cf7eccbd6e17e66b0ed76:dbb40f41e6e9a5c4a9a1fd8d9e6ccf6d92676c92#8976086f07d37e3f6288e2fccf9650ae' (76.4KB)
Upload completed in 3s

$ conan art:promote pkglist.json --from abril-dev --to abril-prod --url=https://xxx/artifactory/ --user=abril --token="xxx"

-------- Promoting _/zlib/1.3.1/_/b8bc2603263cf7eccbd6e17e66b0ed76/export/ --------
Promoted file

-------- Promoting _/zlib/1.3.1/_/b8bc2603263cf7eccbd6e17e66b0ed76/package/dbb40f41e6e9a5c4a9a1fd8d9e6ccf6d92676c92/8976086f07d37e3f6288e2fccf9650ae --------
Promoted file

$ conan remove "*" -c -r=prod
Connecting to remote 'prod' with user 'abril'
Found 1 pkg/version recipes matching * in prod
Remove summary:
prod
  zlib/1.3.1#b8bc2603263cf7eccbd6e17e66b0ed76: Removed recipe and all binaries

$ conan remove "*" -c -r=dev
Connecting to remote 'dev' with user 'abril'
Found 1 pkg/version recipes matching * in dev
Remove summary:
dev
  zlib/1.3.1#b8bc2603263cf7eccbd6e17e66b0ed76: Removed recipe and all binaries

At this point my remotes look like this:

If I now reupload (minus the rebuild in your steps)

$ conan upload "zlib/1.3.1#b8bc2603263cf7eccbd6e17e66b0ed76:dbb40f41e6e9a5c4a9a1fd8d9e6ccf6d92676c92" -r=dev -f=json > pkglist.json

======== Uploading to remote dev ========

-------- Checking server for existing packages --------
zlib/1.3.1: Checking which revisions exist in the remote server
Connecting to remote 'dev' with user 'abril'

-------- Preparing artifacts for upload --------

-------- Uploading artifacts --------
zlib/1.3.1: Uploading recipe 'zlib/1.3.1#b8bc2603263cf7eccbd6e17e66b0ed76' (6.4KB)
zlib/1.3.1: Uploading package 'zlib/1.3.1#b8bc2603263cf7eccbd6e17e66b0ed76:dbb40f41e6e9a5c4a9a1fd8d9e6ccf6d92676c92#8976086f07d37e3f6288e2fccf9650ae' (76.4KB)
Upload completed in 2s

$ conan art:promote pkglist.json --from abril-dev --to abril-prod --url=https://xxx/artifactory/ --user=abril --token="xxx"

-------- Promoting _/zlib/1.3.1/_/b8bc2603263cf7eccbd6e17e66b0ed76/export/ --------
Promoted file

-------- Promoting _/zlib/1.3.1/_/b8bc2603263cf7eccbd6e17e66b0ed76/package/dbb40f41e6e9a5c4a9a1fd8d9e6ccf6d92676c92/8976086f07d37e3f6288e2fccf9650ae --------
Promoted file

The promotion successfuly finishes

[klausholstjacobsen]

My artifactory version is 7.71.23.
It looks like that is indeed very old. I am however only a small cog in a large coorporation and have no control over this!

[AbrilRBS]

What we could do is to add an opt-in way to ensure a clean promotion is performed, ie, that the promote could clear up any leftover folders before promoting. This might defeat the benefits of deduplication etc, but might solve cases like yours. Would being able to perform the promotion in an "erase and write" way work to solve your case?