Pinned builds generate output files with filenames which are not known ahead of time

[matthewdarwin]

When writing automation around pinned builds, it is not possible to know ahead of time what the name of the files produced will be. This means that automation has to use shell wildcards to get the filenames.

Would be better if the build outputted a file with the name in it or other way to avoid globbing which might result in the wrong thing being found in the future if the build process changes.

Current assets are named:

• leap_5.0.0-rc2_amd64.deb
• leap-5.0.0-rc2-x86_64.tar.zst

[bhazzard]

@matthewdarwin can you clarify what you mean by "a file with the name in it"?

[matthewdarwin]

something I can do cat filename which returns 5.0.0-rc2

[spoonincode]

Not sure it helps your use case, but one thing you can do is to output the files in to a new/empty directory. -o outputdir instead of the -o . as given in instructions.

[bhazzard]

Spoke to Matthew today to better understand how he uses this. He uses the zipped output rather than the debian package to produce his own debian package. He does this because his custom debian contains some custom scripts (especially for start/stop).

Outputting to a specific directory is a sufficient workaround. It would be even better if the files weren't zipped, so he didn't have to ls | grep to get the file name of the zip.