feature(argus): Release Planner #459
Open
Conversation
This file contains 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
k0machi
force-pushed
the
release-planner-rework
branch
4 times, most recently
from
664c673
to
af28233
Compare
k0machi
force-pushed
the
release-planner-rework
branch
3 times, most recently
from
9eb0110
to
d1ec135
Compare
k0machi
force-pushed
the
release-planner-rework
branch
from
d1ec135
to
6df59a7
Compare
soyacz
reviewed
Oct 2, 2024
k0machi
force-pushed
the
release-planner-rework
branch
4 times, most recently
from
4a711e4
to
ee8766c
Compare
This commit adds a new way to manage releases inside Argus, called Release Planner. Release Planner replaces current Release Scheduling mechanism (but not the Duty Calendar for now). Main features include: * Plans are now separate entities (replacing one global release schedule) * Each plan contains tests, groups and people it will be using for assignments * Plans can target a specific scylla version to scope the plan to a point or RC release. * Plans can be edited, deleted and copied. * On copy, plan will offer to replace missing tests/groups if it is being copied to another release and that release is missing required tests. * Each plan automatically creates and maintains a view dashboard for said plan and can be viewed from plan overview page or inside views overview * The new assignment logic is now applied to all releases not marked as "endless" (perpetual in the admin panel). Currently the only one that is marked that way is scylla-master. Fixes scylladb#377 Task: scylladb/qa-tasks#1717
k0machi
force-pushed
the
release-planner-rework
branch
from
ee8766c
to
8204735
Compare
soyacz
approved these changes
Oct 9, 2024
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.
This PR adds a new way to manage releases inside Argus, called
Release Planner. Release Planner replaces current Release Scheduling
mechanism (but not the Duty Calendar for now). Main features include:
schedule)
assignments
point or RC release.
being copied to another release and that release is missing required
tests.
said plan and can be viewed from plan overview page or inside views
overview
"endless" (perpetual in the admin panel). Currently the only one that
is marked that way is scylla-master.
Task: #377
Task: https://github.com/scylladb/qa-tasks/issues/1717