Skip to content

Add job to copy packages built in 2025 from robostack-staging to robostack-noetic and robostack-humble #68

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

Merged
merged 3 commits into from
Jan 23, 2025

Conversation

traversaro
Copy link
Member

This PR adds a job that runs hourly (or manually triggered) and make sure that any new package uploaded to robostack-staging (newer then a cutoff date, that is set to 2025-01-01 is copied to robostack-noetic or robostack-humble.

To work correctly, we need to set two repository secrets:

  • ROBOSTACK_NOETIC_ANACONDA_API_TOKEN
  • ROBOSTACK_HUMBLE_ANACONDA_API_TOKEN

After the CI job is active, we can simply document that to install newly built packages packages for distro <distro> you need to use the channel robostack-<distro>, as that is the location for all the currently supported distros:

  • noetic (thanks to this CI job)
  • humble (thanks to this CI job)
  • jazzy (as the packages were directly uploaded to robostack-jazzy)

@Tobias-Fischer
Copy link
Contributor

Hi @traversaro - thanks a lot for this!

A few questions:

@traversaro
Copy link
Member Author

https://anaconda.org/robostack-humble already has a decent amount of packages – what should we do with them?

I was just thinking to leave existing packages where they are for reproducibility, what are possible alternative solutions?

https://anaconda.org/robostack-noetic – I don't have access there, could you create the API key and add it here?

Me neither, but I can create it and share it.

@Tobias-Fischer
Copy link
Contributor

https://anaconda.org/robostack-humble already has a decent amount of packages – what should we do with them?

I was just thinking to leave existing packages where they are for reproducibility, what are possible alternative solutions?

https://anaconda.org/robostack-noetic – I don't have access there, could you create the API key and add it here?

Me neither, but I can create it and share it.

Both sounds good, thank you!

@traversaro
Copy link
Member Author

I created the robostack-noetic channel on anaconda.org and uploaded the ROBOSTACK_NOETIC_ANACONDA_API_TOKEN secret to the repo. @Tobias-Fischer I can't find you on anaconda.org, can you send me your user so can I give you access to the robostack-noetic channel?

@Tobias-Fischer
Copy link
Contributor

I'm "TobiasRobotics" on anaconda.org :)

@Tobias-Fischer
Copy link
Contributor

I've added the humble API token - let's see if this works :)

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