Skip to content

Updated debian package CI build#564

Open
marip8 wants to merge 1 commit into
tesseract-robotics:masterfrom
marip8:update/deb-package-ci-job
Open

Updated debian package CI build#564
marip8 wants to merge 1 commit into
tesseract-robotics:masterfrom
marip8:update/deb-package-ci-job

Conversation

@marip8

@marip8 marip8 commented May 29, 2026

Copy link
Copy Markdown
Contributor

Updates the debian package build CI job to be triggered correctly for past versions. Corresponds to tesseract-robotics/tesseract_planning#750

@Levi-Armstrong

Copy link
Copy Markdown
Contributor

@marip8 Does this change now require it to only be manually triggered or does it still work as expected when generating a release?

@marip8

marip8 commented May 30, 2026

Copy link
Copy Markdown
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants