search

conda-forge / conda-forge-ci-setup-feedstock

A conda-smithy repository for conda-forge-ci-setup.
BSD 3-Clause "New" or "Revised" License
13 stars 50 forks source link

Remove recipe content from output of `inspect_artifacts`? #328

Open h-vetinari opened 1 week ago

h-vetinari commented 1 week ago

I love the new inspect_artifacts stage, it's great to see what ends up in various outputs within the respective CI run! 👏

I'm wondering thought bout displaying all the recipe content that's under /info - I think this information is pretty useless (it's readily available in the feedstock anyway), and it blows up the inspection stage unnecessary. For example, even a completely empty metapackage gets:

win-64\flang_win-64-19.0.0.dev0-hdd2dbb4_2.conda
------------------------------------------------
-- Size: 12.7KB
-- SHA256: 714113da845bf16223d2aa16c6cf7eb0ef831d36b30b0298562c04596658a374
-- Contents:
?rw-rw-rw- 0/0       9909 2024-06-28 19:07:29 info/about.json 
?rw-rw-rw- 0/0          0 2024-06-28 19:07:29 info/files 
?rw-rw-rw- 0/0          0 2024-06-28 19:07:29 info/git 
?rw-rw-rw- 0/0         81 2024-06-28 19:07:29 info/hash_input.json 
?rw-rw-rw- 0/0        320 2024-06-28 19:07:29 info/index.json 
?rw-rw-rw- 0/0      13151 2024-06-25 21:42:29 info/licenses/flang/LICENSE.TXT 
?rw-rw-rw- 0/0         42 2024-06-28 19:07:29 info/paths.json 
?rw-rw-rw- 0/0        644 2024-06-28 19:07:29 info/recipe/conda_build_config.yaml 
?rw-rw-rw- 0/0       1116 2024-06-28 19:07:29 info/recipe/meta.yaml 
?rwxrwxrwx 0/0        328 2024-06-28 13:48:18 info/recipe/parent/activate.bat 
?rw-rw-rw- 0/0        763 2024-06-28 13:48:18 info/recipe/parent/activate.sh 
?rwxrwxrwx 0/0       1033 2024-06-28 13:48:18 info/recipe/parent/bld.bat 
?rw-rw-rw- 0/0        943 2024-06-28 13:48:18 info/recipe/parent/build.sh 
?rw-rw-rw- 0/0        178 2024-06-28 13:48:18 info/recipe/parent/conda_build_config.yaml 
?rwxrwxrwx 0/0         40 2024-06-28 13:48:18 info/recipe/parent/deactivate.bat 
?rw-rw-rw- 0/0        106 2024-06-28 13:48:18 info/recipe/parent/deactivate.sh 
?rw-rw-rw- 0/0         61 2024-06-28 13:48:18 info/recipe/parent/hello_world.f90 
?rwxrwxrwx 0/0        496 2024-06-28 13:48:18 info/recipe/parent/install_flang.bat 
?rw-rw-rw- 0/0        259 2024-06-28 13:48:18 info/recipe/parent/install_flang.sh 
?rwxrwxrwx 0/0        106 2024-06-28 13:48:18 info/recipe/parent/install_libflang.bat 
?rw-rw-rw- 0/0        270 2024-06-28 13:48:18 info/recipe/parent/install_libflang.sh 
?rw-rw-rw- 0/0       3739 2024-06-28 13:48:18 info/recipe/parent/meta.yaml 
?rw-rw-rw- 0/0       1568 2024-06-28 13:48:18 info/recipe/parent/recipe-scripts-license.txt 
?rw-rw-rw- 0/0         38 2024-06-28 19:07:29 info/run_exports.json

And in multi-output recipes, every output gets a copy of that redundant information... I think it'd be much more preferable to just remove anything under /info, or at least make it opt out. Looking at the implementation here and in conda-package-handling, this will probably need some feature-work there (unless we do some regex-filtering on the output of list_contents).

CC @jaimergp

jaimergp commented 6 days ago

I think we can add a flag, like cph list --no-info or cph list --exclude?. Let me look into it.

jaimergp commented 6 days ago

With https://github.com/conda/conda-package-handling/pull/253 we will be able to do --components=pkg for .conda artifacts.