SENJUN-26: reuse containers with same language and different action #23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ShipilovDmitry
force-pushed
the
SENJUN-26-common-containers
branch
from
54630c8 to
f1b2da2
Compare
Microvenator
approved these changes
Apr 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Кардинально изменена логика выбора контейнера для выполнения кода.
Раньше запустить код для задачи в главе, плейграунда и практики можно было только в специально предназначенном для данного типа «задачи» контейнере. Из-за этого мы могли «простаивать», когда все контейнеры плейграунда заняты, а контйенеры глав свободны.
Теперь есть разделение только по языкам программирования. Любой тип задачи, например, для питона может быть запущен в свободном контейнере питона. И так для всех языков программирования.