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

Migrate CI/CD from gitlab to github #1

Closed
14 tasks done
AhmetNSimsek opened this issue Jan 18, 2024 · 2 comments
Closed
14 tasks done

Migrate CI/CD from gitlab to github #1

AhmetNSimsek opened this issue Jan 18, 2024 · 2 comments
Assignees

Comments

@AhmetNSimsek
Copy link
Collaborator

AhmetNSimsek commented Jan 18, 2024

from: FZJ-INM1-BDA/siibra-python#540 (comment)

CI pipelines to be migrated:

  • Migrate CI/CD pipeline ci:checklist:generate-update
  • Migrate CI/CD pipeline ci:test:check_connectivity_json
  • Migrate CI/CD pipeline ci:test:check_schema
  • Migrate CI/CD pipeline ci:test:check_jsons
  • Migrate CI/CD pipeline ci:test:check_ebrains_id
  • Migrate CI/CD pipeline ci:test:check_map_volume_idx
  • Migrate CI/CD pipeline ci:test:region_attr_compliance
  • Migrate CI/CD pipeline ci:test:check_maps
  • Migrate CI/CD pipeline ci:test:check_maps_precompmesh
  • Migrate CI/CD pipeline mirror:push_to_mirror
  • Migrate CI/CD pipeline deploy:okd:sync_to_okd
  • Migrate CI/CD pipeline deploy:okd:restart_server_pod
  • Migrate CI/CD pipeline deploy:okd:get_api_queues
  • Migrate CI/CD pipeline deploy:okd:start_new_worker_pods
@xgui3783 xgui3783 changed the title Introduce CI/CD Migrate CI/CD from gitlab to github Jan 18, 2024
@xgui3783
Copy link
Member

re: migration of actions prefixed deploy: these actions are needed for data validations.

Currently, ebrain2.0 infrastructure resource quota is too limited to deploy another instance of siibra-api. (this is after we quadrepled our quota in the last month).

This leaves us with a few options:

  • ask the quota at ebrain to be increased again
  • deploy an instance of siibra-api else where (e.g. julich VM?)

will check how feasible it is to deploy it at julich.

@AhmetNSimsek
Copy link
Collaborator Author

Deploy workflow was added with #36, which completes all the todos.

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

No branches or pull requests

2 participants