Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Restrict upload to built packages

See original GitHub issue

ConanMultiPackager uses conan upload --all, which uploads all existing packages with matching reference. The expected behaviour would be to upload only the packages built in this run.

v0.10.4

Issue Analytics

State:
Created 6 years ago
Comments:11 (5 by maintainers)

Top GitHub Comments

1reaction

spiderkeyscommented, Sep 6, 2018

I’m running into the same issue.

It’s not really a problem that it tries to upload things for a second time. As you mentioned, re-uploads will already match the uploaded packages and will be skipped. The main issue is that it re-compresses the recipe multiple times, and in some of my projects, the compression step can take quite a long time.

For a project that has four build configurations, it looks like it properly calls conan create four times, but then calls conan upload --all on each step, which tries to compress and upload 1, 2, 3, and 4 packages for each conan create call, respectively.

0reactions

danimtbcommented, Sep 10, 2018

@wpalfi Yes, first recipe installed is the first one of the json output as this is the first node of the dependency graph that is processed.

Top Results From Across the Web

Configuring a package's access control and visibility

Container creation visibility for organization members On the left, click Packages. Under "Container creation", choose whether you want to enable the creation ...

How to disable uploading a package to PyPi unless

What I'd like to do is create a proper subclass of the upload command called SafeUpload and have it check for the --public...

Restrict which packages are installable from a repository

You'll end up with the following behaviour: $ sudo apt install moosefs-client/bullseye-backports Reading package lists... Done Building ...

Prevent Twine From Uploading to Public PyPi - Packaging

Another thing you can do is give all your packages an invalid Trove classifier that your private repo accepts (something like “Private ::...

5. Managing Packages — developers-reference 12.9 ...

Each upload needs to specify which distribution the package is intended for. The package build process extracts this information from the first line...