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.

Sign up for GitHub

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

Jump to bottom

Separate CI checks for each service #79

Open
Eason0729 opened this issue Aug 28, 2024 · 0 comments
Open

Separate CI checks for each service #79

Eason0729 opened this issue Aug 28, 2024 · 0 comments
Labels
C-CI/CD Relate to CI/CD good first issue Good for newcomers P-Low Low priority

Comments

@Eason0729
Copy link
Contributor

We found it better to have separated CI check for each service(frontend, backend, judger).

This issue might make it easier to debug, but also make runner cache more precious.

We decide to go for it, because cache already running out constantly even without this approach
@Eason0729 Eason0729 added P-Low Low priority good first issue Good for newcomers C-CI/CD Relate to CI/CD labels Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-CI/CD Relate to CI/CD good first issue Good for newcomers P-Low Low priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Eason0729