snapcrafters / ci

Repository for shared CI tools and actions
https://github.com/snapcrafters/.github/wiki
MIT License
3 stars 7 forks source link

[Bug]: Release to Candidate does not work with adopt-info #47

Open pedro-avalos opened 1 month ago

pedro-avalos commented 1 month ago

What happened?

The Release to Candidate action failed to find the snapped package after the remote build finished because the version information was purposefully blank/null (using adopt-info for the version metadata). The workflow could not find the .snap file because the version was null instead of the version that was adopted at build-time.

What should have happened?

Perhaps the workflow should accept any <name>_*_<arch>.snap or even <name>_*.snap file as a valid output of the remote build.

Output of snap info $snap_name

n/a

Output of snap connections $snap_name

n/a

Output of snap version

n/a

Relevant log output

[...]
Creating snap package...
Packed gpu-burn_9aefd7c_amd64.snap
[...]
Revoking proxy token...
[...]
Could not find gpu-burn_null_amd64.snap

Teminal output of app

No response

pedro-avalos commented 1 month ago

Ah, I just saw there is a PR for this #46