Updated debian package CI build#564
Conversation
|
@marip8 Does this change now require it to only be manually triggered or does it still work as expected when generating a release? |
|
It probably won't work when a new tag is pushed to the repo because it extracts the required version information from user inputs which probably only get populated by a user dispatch. That said, I don't think there is a currently a purpose to running this job when a new tag is pushed because the action does not upload the artifacts anywhere, and Github deletes them after a certain amount of time. I don't think I'm opposed to making this a fully manual CI job because it seems like the debians are currently being attached to releases manually anyway. The other option is to make this job run on releases only (not pushed tags), and to find a way to upload the debs as an artifact to the release for which it was run. That seems like it should be possible |
Updates the debian package build CI job to be triggered correctly for past versions. Corresponds to tesseract-robotics/tesseract_planning#750