Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Add workflow that builds and releases cache on new tags #42984

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

oysstu
Copy link
Contributor

@oysstu oysstu commented Sep 29, 2024

This PR contains a simple workflow to generate and release a cache from each pushed tag. This would make targeting specific snapshots using rosdep and rosinstall_generator more convenient. The compressed archive is fairly small and does not take long to generate since it bases it off the current index cache.

Let me know if this makes sense to have running and if any changes are needed.

Co-authored-by: Tomoya Fujita <[email protected]>
@tfoote
Copy link
Member

tfoote commented Oct 2, 2024

Overall doing this to have the cache items with the tags sounds interesting. The tools were designed to work without a cache being necessary but they will be much slower. What do you use for configuring the tools to find the release artifacts?

@oysstu
Copy link
Contributor Author

oysstu commented Oct 3, 2024

Overall doing this to have the cache items with the tags sounds interesting. The tools were designed to work without a cache being necessary but they will be much slower. What do you use for configuring the tools to find the release artifacts?

Not sure I understand the question. Are you referring to the release artifacts output by this workflow? They should be available at the following url (if using bash).

<repo>/releases/download/${TAG}/${TAG%%/*}-${TAG#*/}-cache.yaml.gz

I've been rosinstall_generator by modifying the cache url in index-v4.yaml and setting ROSDISTRO_INDEX_URL. If I check out this repository at a specified tag and leave the cache url unmodified, it will output the wrong versions (e.g. jazzy/2024-05-23 should generate rosbag2 with version 0.26.3, but it outputs 0.26.5). I just realized that this behavior is probably a bug in rosintall_generator.

@cottsay cottsay added the persistent Issue/PR won't be marked as stale if inactive for a while. label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
persistent Issue/PR won't be marked as stale if inactive for a while.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants