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

Handle dependencies between sidecars in plugin-registry #18363

Open
benoitf opened this issue Nov 13, 2020 · 3 comments
Open

Handle dependencies between sidecars in plugin-registry #18363

benoitf opened this issue Nov 13, 2020 · 3 comments
Labels
area/plugin-registry kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.

Comments

@benoitf
Copy link
Contributor

benoitf commented Nov 13, 2020

Is your task related to a problem? Please describe.

Some sidecars in che-plugin-registry are dependent from other sidecars.
For now it requires a 2-step phase where base image is updated and then child image can be updated

Describe the solution you'd like

Handle automatically internal dependencies between sidecars of the same repository in one phase.

Describe alternatives you've considered

ready to listen for other proposals

Additional context

as monorepo, the idea behind is that in one single PR you can update several items at once.

Part of #15819
@benoitf benoitf added kind/task Internal things, technical debt, and to-do tasks to be performed. area/plugin-registry labels Nov 13, 2020
@benoitf benoitf mentioned this issue Nov 13, 2020
Closed
18 tasks
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 13, 2020
@sleshchenko sleshchenko added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Nov 13, 2020
@sleshchenko
Copy link
Member

assigning p1 since it's what the related epic has

@ericwill
Copy link
Contributor

Couldn't dependabot handle most of this for us?

@gattytto gattytto mentioned this issue Dec 10, 2020
Closed
@che-bot
Copy link
Contributor

che-bot commented May 18, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 18, 2021
@ericwill ericwill added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/plugin-registry kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@benoitf @sleshchenko @ericwill @che-bot