Migrate non-recipe repos from co-op cloud org -> toolshed #666
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The new version of #569. The number of the beast!
Remaining repos left on the co-op cloud org below.
They should all be migrated to toolshed.
(UPDATE: see below for moar migration tickets)
abrashithttps://git.coopcloud.tech/coop-cloud/abrahttps://git.coopcloud.tech/coop-cloud/exampleCANNOT BE MIGRATED YEThttps://git.coopcloud.tech/coop-cloud/godotenvhttps://git.coopcloud.tech/coop-cloud/abra-test-recipeweb/docs shit
https://git.coopcloud.tech/coop-cloud/docs.coopcloud.techhttps://git.coopcloud.tech/coop-cloud/coopcloud.techcatalogue shit
https://git.coopcloud.tech/coop-cloud/recipes.coopcloud.techhttps://git.coopcloud.tech/coop-cloud/recipes-catalogue-jsonhttps://git.coopcloud.tech/coop-cloud/auto-recipes-catalogue-jsontest shit
https://git.coopcloud.tech/coop-cloud/drone-abrahttps://git.coopcloud.tech/coop-cloud/docker-cp-deployhttps://git.coopcloud.tech/coop-cloud/stack-ssh-deployotherhttps://git.coopcloud.tech/coop-cloud/coop-cloud-appsabrasource code refsHere's all the refs to
git.coopcloud.techon latestabrarelease:decentral1se referenced this issue2025-01-03 07:41:55 +00:00
Should we migrate in reverse order? other -> test -> catalogue etc. (fixing along the way?) I think we can't migrate
examplewithout breaking previousabrareleases (it's what is cloned for a new recipe), so it will have to stay for a while longer? technically it is a "recipe" 🙃decentral1se referenced this issue from toolshed/abra2025-01-03 07:53:29 +00:00
https://git.coopcloud.tech/toolshed/coop-cloud-apps
https://git.coopcloud.tech/toolshed/docker-cp-deploy
toolshed/docker-cp-deploy#7
https://git.coopcloud.tech/toolshed/drone-abra
toolshed/drone-abra#6
https://git.coopcloud.tech/toolshed/stack-ssh-deploy
toolshed/stack-ssh-deploy#10
https://git.coopcloud.tech/toolshed/auto-recipes-catalogue-json
toolshed/auto-recipes-catalogue-json#4
https://git.coopcloud.tech/toolshed/recipes-catalogue-json
toolshed/recipes-catalogue-json#7
https://git.coopcloud.tech/toolshed/recipes.coopcloud.tech
toolshed/recipes.coopcloud.tech#37
https://git.coopcloud.tech/toolshed/coopcloud.tech
toolshed/coopcloud.tech#49
https://git.coopcloud.tech/toolshed/docs.coopcloud.tech
toolshed/docs.coopcloud.tech#264
https://git.coopcloud.tech/toolshed/abra-test-recipe
https://git.coopcloud.tech/toolshed/godotenv
https://git.coopcloud.tech/toolshed/abra
abrastill working apparently 🤷🤷🤷 More manual testing...I've migrated the
abracontainer package. Here's what I did:docker logindocker build -t git.coopcloud.tech/toolshed/abra .docker push git.coopcloud.tech/toolshed/abratoolshedpackages tababracontainer with theabrarepo packagesabra-botuser account (forgot password 🙈 DM me for a copy). This is the account used for the matrix notifications "back in the day". It can be used as a shared account for general automation? I generated a token for package repo automation (DM me for a copy)abra-botto the toolshed robot org teamabra-botand addedgit_coopcloud_tech_token_abra_botas a secret using the CLI:drone secret add --repository toolshed/abra --name git_coopcloud_tech_token_abra_bot --data "..." --allow-push-on-pull-request --allow-pull-request(see #666 (comment) for a better way of doing this)@3wordchant lemme know what you think but if you could add
git_coopcloud_tech_token_abra_botas an "orgsecret" for thetoolshedorg on https://build.coopcloud.tech then it would be available for the CI builds.Something like:
drone orgsecret add toolshed git_coopcloud_tech_token_abra_bot "<token>" --allow-push-on-pull-request --allow-pull-requestI'll DM you the token now.
I can't seem to do this as it requires "system administration permissions" according to the docs. Maybe you need to run that in the container of the Drone deployment itself?
Done. A bit unsure about
--allow-push-on-pull-request --allow-pull-requestbecause my understanding is this means anyone with a git.coopcloud.tech account (including drive-by github / gitlab logins) can now read out the token. But I went with it for now.Only the
coopcloudaccount has permissions to edit orgsecrets, I think. LMK if you need the password for that again.Also while we're smashing CI to pieces maybe a good moment to migrate away from my personal token, #668
There's still bits & bobs to be done but this mostly "done".