Repository navigation
Remove the staging copy job - #205
Conversation
|
Thanks @Tobias-Fischer. It is not completely clear to me though why this would be added to this repo, since this repo is about the robostack website |
I think because we had a similar robostack-staging --> robostack-humble job in https://github.com/RoboStack/robostack.github.io/blob/main/.github/workflows/copy-staging-packages.yml . |
|
I’m happy to move this to the monorepo, it will be better placed there! |
The staging copy (scripts/copy-to-distro-specific-channel.py and the hourly copy-staging-packages workflow) now lives in RoboStack/robostack#97, together with the prefix.dev -> anaconda.org mirror. With it go its tests (the last ones here: pytest, the test task and its CI step) and anaconda-client. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
42a98d8 to
029cdee
Compare
Tobias-Fischer
changed the title
Yeah agreed. Should we close this PR then? |
I repurposed this PR to remove the copy script here .. is that ok? So we still need it. I changed description as well. |
|
Sounds good! |
…da.org mirror From RoboStack/robostack.github.io: tools/copy_staging_packages.py (was scripts/copy-to-distro-specific-channel.py) copies humble's and noetic's packages from robostack-staging on to their own channels, hourly as before; tools/mirror_to_anaconda.py (from RoboStack/robostack.github.io#205) uploads what a prefix.dev channel has and its old anaconda.org channel doesn't, started by hand until the prefix.dev channels exist. A job without its token secret is skipped, so nothing fails before the secrets are set here. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # .github/workflows/copy-staging-packages.yml
Tobias-Fischer
changed the title
|
@RoboStack/robostack-core this needs a review please |
…#567) * Upload to and read from robostack-noetic instead of robostack-staging robostack-staging only reached users of robostack-noetic through the hourly copy job in RoboStack/robostack.github.io, which goes away with RoboStack/robostack.github.io#205. robostack-noetic already has every current noetic build (the copy job ran since 2025-01-01), so skip_existing against it doesn't trigger rebuilds. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * [skip ci] hold CI; drop this commit before merging --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
Related: RoboStack/ros-noetic#567 |
3 participants
This repository now only hosts the website; the hourly staging copy goes away:
scripts/copy-to-distro-specific-channel.py, its test, and the hourlycopy-staging-packages.yml.robostack-staging→robostack-noetic).robostack-<distro>(Per-distribution uploads to prefix.dev and/or anaconda.org; humble off robostack-staging robostack#120), and noetic does too with Upload to and read from robostack-noetic instead of robostack-staging ros-noetic#567.Without the copy script's tests no Python tests are left here, so
pytest, thetesttask and its step inchecks.ymlgo as well, and so doesanaconda-client.niquests/py-rattlerstay for the package-table scripts.Merge together with RoboStack/ros-noetic#567: until that lands, new noetic builds still go to
robostack-stagingonly.🤖 Generated with Claude Code