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

Initial setup of Che Defvile registry #13353

Closed
5 tasks done
skabashnyuk opened this issue May 17, 2019 · 2 comments
Closed
5 tasks done

Initial setup of Che Defvile registry #13353

skabashnyuk opened this issue May 17, 2019 · 2 comments
Assignees
@sleshchenko
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.

Comments

@skabashnyuk
Copy link
Contributor

skabashnyuk commented May 17, 2019 •
edited by sleshchenko
Loading

Description

  • Create a repository in che-incubator until we will have eclipse/che-devfile-registry in place
  • Setup images build
  • Adjust Che deployment scripts in the same way as we have with plugin registry.
  • Add ability to get devfile registry from API.
  • Add Che7 stacks to this registry from stacks.json
@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform severity/P1 Has a major impact to usage or development of the system. labels May 17, 2019
@slemeur slemeur mentioned this issue May 17, 2019
Closed
6 tasks
@sleshchenko sleshchenko mentioned this issue May 17, 2019
Closed
This was referenced May 17, 2019
Closed
Closed
@sleshchenko sleshchenko self-assigned this May 17, 2019
@sleshchenko sleshchenko added the status/in-progress This issue has been taken by an engineer and is under active development. label May 17, 2019
@gorkem
Copy link
Contributor

gorkem commented May 18, 2019

@deboer-tim I think you had some ideas on how to organize stacks in a registry. This is the moment to voice them :)

This was referenced May 21, 2019
Closed
Closed
This was referenced May 21, 2019
Merged
Merged
@sleshchenko sleshchenko removed the status/in-progress This issue has been taken by an engineer and is under active development. label May 27, 2019
@sleshchenko sleshchenko mentioned this issue May 27, 2019
Merged
@l0rd l0rd mentioned this issue May 28, 2019
Closed
@deboer-tim
Copy link

Gorkem - Sorry for the delayed response, was on vacation when the notification came and it got buried. Mario setup a call on Friday, we'll discuss there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sleshchenko sleshchenko

Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. 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
@gorkem @skabashnyuk @sleshchenko @deboer-tim